feat: adopt codex batch tool (safe code-mode core) - #225
Merged
Conversation
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
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
Follow-up to the codex adoption audit (#224). Implements the safe, high-value core of codex's Code Mode without an embedded script runtime:
Batchtool: runs a list of read-only tool calls in a single turn, cutting agent round-trips for fan-out research.tool.IsReadOnly) are accepted; every inner call resolves through the session registry, schema-validates, and executes individually. No mutation can bypass the normal tool pipeline.docs/plans/codex-adoption-plan.md: marks Batch as the adopted safe core of Code Mode; keeps full arbitrary-script Code Mode, agent-identity signing, and cloud-tasks as explicitly deferred RFCs (already covered byinternal/identity+ HMAC-chainedinternal/securitylog/ Hawk Cloud respectively).Test plan
go test ./...green (twice — locally and via pre-push hook)make vet,make lint,hawk verifygreenmarkdownlint-cli2clean on updated doc