docs(architecture): document Desktop's two spawn paths for buzz-acp - #6210
Open
shawnhank wants to merge 2 commits into
Open
docs(architecture): document Desktop's two spawn paths for buzz-acp#6210shawnhank wants to merge 2 commits into
shawnhank wants to merge 2 commits into
Conversation
ARCHITECTURE.md covered buzz-acp's own internals in detail but never explained its relationship to the Desktop app that normally launches it — specifically, that Desktop spawning buzz-acp as a child process is one option among two, and that an independently-launched buzz-acp process (e.g. under a separate, restricted OS account via launchd) participates in channels identically, just outside Desktop's own process tree and "Agents" panel. Add a short subsection to the buzz-acp entry covering both spawn paths, citing the exact spawn call and env vars, so this doesn't have to be re-derived from source every time it comes up. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Shawn Hank <shawn@shawnhank.com>
Per feedback: the two-spawn-path explanation landed after a lot of back-and-forth in chat, and a diagram would have gotten there faster, especially for non-technical readers. Adds a Mermaid flowchart (renders natively in GitHub's markdown) showing the two OS accounts, both spawn paths, and all three independent relay connections, plus a one-sentence plain-language framing above it. Rendered locally with @mermaid-js/mermaid-cli to confirm the diagram is valid before pushing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Shawn Hank <shawn@shawnhank.com>
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
1 participant
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
ARCHITECTURE.mddocumentsbuzz-acp's own internals in detail, but never explains its relationship to the Desktop app that normally launches it.buzz-acpas a child process (inheriting Desktop's OS account) is one option, and thatbuzz-acpcan instead be launched independently (e.g. vialaunchd/systemdunder a separate, more restricted account) with identical channel-level behavior — it just won't appear in Desktop's "Agents" panel, since that panel only tracks locally-spawned children.Adds a short, source-cited subsection to the existing
buzz-acpentry covering both spawn paths, so this doesn't need to be re-derived from source every time it comes up.Test plan
desktop/src-tauri/src/managed_agents/runtime.rs:521,532-533)VISION.mdfor any conflicting stance on agent isolation — none found🤖 Generated with Claude Code