Repository navigation
Conversation
loganj
force-pushed
the
agents-runner-page
branch
from
October 29, 2026 13:55
63430de to
56d8d5b
Compare
loganj
added a commit
that referenced
this pull request
Oct 29, 2026
The Runner becomes its own service, apart from the Manager, and on macOS it runs in a hidden "agents" webview that the system never throttles, with its storage and the plugins' agent entries. The screens' page keeps the Manager. Only JSON crosses, over the native agents port, on two lanes: "agents" for the Manager and Runner link, and "page" for where agent storage is, the followed communities, and local activity. - The Runner owns presence, keep-awake, agent hooks and the reconnect of its own connections. A failed relay is retried at most every 30 s, whichever owner asks. - The Manager waits at most 10 s for the Runner's first decision. - The agents page starts the Runner once the screens' page says where agent storage is; the screens' page still loads and moves it first. - Other platforms keep the Runner in the screens' page. Includes #1735 (page-owned native work), #1743 and #1744's native page. Squashes #1892 and #1893. Signed-off-by: Logan Johnson <loganj@squareup.com> Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
loganj
changed the base branch from
agents-runner-service
to
agents-link-running
October 29, 2026 13:55
This was referenced Oct 29, 2026
Draft
The Runner becomes its own service, apart from the Manager, and on macOS it runs in a hidden "agents" webview that the system never throttles, with its storage and the plugins' agent entries. The screens' page keeps the Manager. Only JSON crosses, over the native agents port, on two lanes: "agents" for the Manager and Runner link, and "page" for where agent storage is, the followed communities, and local activity. - The Runner owns presence, keep-awake, agent hooks and the reconnect of its own connections. A failed relay is retried at most every 30 s, whichever owner asks. - The Manager waits at most 10 s for the Runner's first decision. - The agents page starts the Runner once the screens' page says where agent storage is; the screens' page still loads and moves it first. - Other platforms keep the Runner in the screens' page. Includes #1735 (page-owned native work), #1743 and #1744's native page. Squashes #1892 and #1893. Signed-off-by: Logan Johnson <loganj@squareup.com> Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
loganj
force-pushed
the
agents-runner-page
branch
from
October 29, 2026 14:54
56d8d5b to
cadac4c
Compare
loganj
force-pushed
the
agents-link-running
branch
from
October 29, 2026 14:54
23ea463 to
471470c
Compare
This was referenced Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Runner becomes its own service, apart from the Manager. On macOS it runs in a hidden
agentswebview, which the system never throttles. That page has the agent storage and the plugins' agent entries. The screens' page keeps the Manager.Only JSON crosses, over the native agents port, on two lanes:
agents: the Manager and Runner link;page: where agent storage is, the followed communities, and local activity.Details:
Value: on macOS, agents keep running when the app's window is hidden or throttled.
This is column 4 of 4 in the Manager/Runner split. It squashes #1892 and #1893. It also carries #1735 (native work belongs to the webview that started it) and the native page parts of #1743 and #1744. #1735 can merge first; this PR then drops its copy.
Stack
main.Validation at
cadac4c1atscis clean, andcargo fmt --checkpasses.mainon this machine (2 emoji-picker theme tests and one StatusEditor test).agent-*.spec.mjsandlocal-agent-activity.spec.mjs): 53 of 53 pass at56d8d5b59. The only change since then is Cross between the Manager and the Runner only over the JSON link #1833's test-fixture fixes, plus one listener binding in the Claude and Codex tabs.nsec_backupkeychain tests failed under the full parallel run and pass on their own; this PR does not touch that code.Deferred: a real
just desktoprun on macOS. It is the only check that runs the hidden page and the native port together. Also a human test in the app.🤖 Generated with Claude Code