Each project is one Boot Camp knowledge git repo under this folder.
Same OAuth as Boot Camp MCP. Then you’ll see projects you can access, grouped by customer.
Select a row for details · Prepare checks out develop
ACCEPTED tasks · Implement locally
File sink under ~/.bootcamp/logs
Loading…
Local to this laptop. Boot Camp repos already include MCP setup — this agent does not write per-project MCP configs.
Save or Re-inject MCP gives every prepared project its own MCP entry, pinned to that project, so two editors on two projects stay apart. On a machine with a single prepared project the shared sfa-bootcamp-user entry is written instead. Both talk to this agent at …, so keep it running, and reload MCP in the IDE afterwards.
Set git credentials on all clones installs the Local Agent credential helper on every prepared Boot Camp repo (and attached nests) so IDE git uses Boot Camp auth instead of Windows Credential Manager / a personal PAT.
Registers in Windows Settings → Apps → Startup as Boot Camp Local Agent.
Tray toasts for task assigned, mentions, and other portal alerts.
Registers this laptop as LOCAL using your signed-in portal OAuth (Developer, Architect, or Admin). Portal never pushes tasks here. Runs start via Implement locally or MCP run_local_execution. CLOUD VM executors still use EXECUTION_SERVER_SECRET on the server — not needed here.
Agent —
—
Updates: download the installer, run it yourself, then restart the agent. Automatic install is temporarily disabled.