feat(agent): bootstrapper type + fix the can_use_tool allow contract - #612
Merged
Conversation
Two findings from the first live blueprint bootstrap:
- The session ran as an implementer, whose ask-lane Bash stalled an
unattended build on its first command. New shipped agent type
`bootstrapper`: shell/edits ride the allow lane (the sandbox is the
isolation boundary — fresh VM, scoped repo token, session-stamped
grant), Task stays denied, deny:["*"] backstops.
- Approvals that WERE granted still failed: the harness's can_use_tool
allow branch now requires `updatedInput` (a record), and orun's bare
{behavior:"allow"} failed the union — every approved call errored
"expected record, received undefined". The driver now remembers each
control request's input and echoes it back unchanged on allow
(backward-compatible: the field was previously optional).
Co-Authored-By: Claude Opus 5 <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
2 participants
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.
Two findings from the first live blueprint bootstrap:
The session ran as an implementer, whose ask-lane Bash stalled an
unattended build on its first command. New shipped agent type
bootstrapper: shell/edits ride the allow lane (the sandbox is theisolation boundary — fresh VM, scoped repo token, session-stamped
grant), Task stays denied, deny:["*"] backstops.
Approvals that WERE granted still failed: the harness's can_use_tool
allow branch now requires
updatedInput(a record), and orun's bare{behavior:"allow"} failed the union — every approved call errored
"expected record, received undefined". The driver now remembers each
control request's input and echoes it back unchanged on allow
(backward-compatible: the field was previously optional).
Co-Authored-By: Claude Opus 5 noreply@anthropic.com