The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
Merge origin/main into fix/swarm-fresh-worktree-and-start-errors
tony6ee3cc960c33
diff --cc cli/src/superTabs/service.tsindex 70b65c190,974efa038..3ac3e1e1a--- a/cli/src/superTabs/service.ts+++ b/cli/src/superTabs/service.ts@@@ -16,7 -16,7 +16,7 @@@ const HELP =messages: 'messages GROUP: read recent messages in a conversation.',message: 'message GROUP MESSAGE_ID: read one exact message, including an earlier question or result referenced by a reply.',post: 'post GROUP TEXT OPERATION_ID [--reply-to MESSAGE_ID] [--attach PATH]...: reply in that conversation. Use a unique ID per message and reuse it after an interrupted request. Answer a message once, with --reply-to its ID. --attach sends a file (a screenshot, a log; up to 10 files of 10 MB each), and TEXT may then be empty.',- start: 'start OPERATION_ID JSON: create one agent in a conversation on a machine you can access. Repeat exactly after an interruption; it follows the same native creation receipt. It does not assign work. With worktree true, the agent starts from the repository\'s default branch, fetched first, unless you set branchRef (refs/heads/BRANCH, or refs/remotes/origin/BRANCH to fetch it first) to start from another branch, such as the one this work builds on.',- start: 'start OPERATION_ID JSON: create one agent in a conversation on a machine in this Swarm\'s Machines list; to use another machine, a person adds it to the Swarm first. Repeat exactly after an interruption; it follows the same native creation receipt. It does not assign work.',++ start: 'start OPERATION_ID JSON: create one agent in a conversation on a machine in this Swarm\'s Machines list; to use another machine, a person adds it to the Swarm first. Repeat exactly after an interruption; it follows the same native creation receipt. It does not assign work. With worktree true, the agent starts from the repository\'s default branch, fetched first, unless you set branchRef (refs/heads/BRANCH, or refs/remotes/origin/BRANCH to fetch it first) to start from another branch, such as the one this work builds on.',resume: 'resume START_ID: finish a pending start without creating another agent.',route: 'route GROUP JSON: before starting or assigning work, choose who does it. JSON: {"difficulty":"low|medium|high","risk":"low|medium|high","why":"one sentence","needs":{"tools":[],"devices":[],"cwd":"/absolute/repo"}}. Start or assign the pick with its routeDecisionId; to choose otherwise, pass overrideReason.',capacity: 'capacity MACHINE_ID JSON: inspect machine, engine and quota headroom. JSON uses the start request fields below. Unknown allowances are not reported as free tokens.',diff --cc docs/swarms.mdindex b53897a4d,b998514ec..b136c75f5--- a/docs/swarms.md+++ b/docs/swarms.md@@@ -51,29 -51,12 +51,35 @@@ tries the other transport (HTTPS or SSHcontributing owner needs access to it on that machine, either through`gh auth login` and `gh auth setup-git` or through an SSH key.+ The lead starts new agents only on the Swarm's listed machines: every+ contributed machine, plus every machine an agent of the Swarm already runs on+ (the lead's own machine is always one of them). To make another machine+ available, a person adds it to the Swarm under Machines; the host then clones+ the project there.++A Builder starts in a new worktree of the project's checkout on that machine.+The host clones a project once and reuses the checkout, so it is not kept up to+date. A start that names no `branchRef` therefore bases its worktree on the+repository's default branch (`origin/HEAD`, else `origin/main` or+`origin/master`), fetched first, rather than on whatever commit the checkout was+left on. If the fetch fails (offline, access refused), the worktree starts from+the copy of that branch the checkout already has; a repository with no `origin`+default branch starts from the checkout's current commit, as before. The lead+passes `branchRef` (`refs/remotes/origin/BRANCH`, fetched first, or+`refs/heads/BRANCH`) to start from another branch, such as the integration+branch the work builds on. This is the Swarm start only: New Harness in Desktop+and the CLI still starts from the folder's current commit unless a branch is+chosen. On the lead's own machine the same rule applies, so work that is only in+the lead's checkout (unpushed commits) reaches a Builder through `branchRef`.++A machine contribution accepts a start in the folder this project uses on that+machine, with one of the engines its owner contributed and the owner's default+account settings. Any other start is refused as `OUTSIDE_CONTRIBUTION`. The+refusal names each refused field (`cwd`, `engine`, or any of `codexHome`,+`gridModel`, `gridName`, `permissionMode`) with what the machine accepts: the+folder this project uses there and the engines it contributes. It does not+repeat the values the start sent.+Ordinary guest machine sharing does not authorize Swarm controls under theowner's account. The owner contributes the machine or an agent. The lead'srouting policy still determines eligible engines, capacity and model choices.