feat(conductor): route code tasks through a sandbox project - #394
Merged
Conversation
The conductor architecture is Conductor → Worker → Sandbox project (each sandbox has its own Claude). A worker runs on the HOST and is NOT sandboxed, so it must not write/run/test a repo's code directly — but it was: e.g. the "add + scan core-agent" chat cloned the repo to /tmp and explored the code on the host instead of spinning up a sandbox. Make the routing explicit in both places a conductor/worker reads: - corral-api SKILL.md: a new "CODE TASKS RUN IN A SANDBOX" section — for any task that edits or executes a repo's code (feature, bug, issue, tests, get an app running, or exploring code to plan such a change), the worker creates a project via POST /projects/create with the coding task as the sandbox `prompt`, then supervises it; non-code work (inspect state, logs/PRs, flows, analysis) stays on the host. - workerContractPreamble: the same rule injected into every worker prompt, so it holds even without the skill. Prompt/skill text only; the skill ships via the asset bundle. No code build needed; worker preamble tests still pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
The conductor architecture is Conductor → Worker → Sandbox project (each sandbox has its own Claude). A worker runs on the HOST and is not sandboxed, so it must not write/run/test a repo's code directly — but it was: e.g. the "add + scan core-agent" global chat cloned the repo to
/tmpand explored the code on the host instead of spinning up a sandbox (confirmed from the conversation logs — it never spawned a worker or created a project for the code part).Change
Make the routing explicit in both places a conductor/worker reads:
corral-api/SKILL.md— a new "CODE TASKS RUN IN A SANDBOX" section: for any task that edits or executes a repo's code (feature, bug, issue, tests, get an app running, or exploring code to plan such a change), the worker creates a project viaPOST /projects/createwith the coding task as the sandboxprompt, then supervises it. Non-code work (inspect state, logs/PRs, flows, analysis) stays on the host.workerContractPreamble— the same rule injected into every worker prompt, so it holds even without the skill.Prompt/skill text only; the skill ships via the asset bundle. No code build needed; worker preamble tests still pass.
🤖 Generated with Claude Code