-
Notifications
You must be signed in to change notification settings - Fork 44
[RefImpl] Codex adapter: tool calls through PreToolUse #170
Copy link
Copy link
Open
Labels
priority:P1Maintainers onlyMaintainers onlyscope:in-focusFeeds the ninety-day committed outcome. Maintainers onlyFeeds the ninety-day committed outcome. Maintainers onlystatus:acceptedIn the backlog. Maintainers onlyIn the backlog. Maintainers onlytype:refimplReference implementation or adapter workReference implementation or adapter workworkstream:coding-agentsOwning workstream. Maintainers onlyOwning workstream. Maintainers only
Description
Activity
Metadata
Metadata
Assignees
Labels
priority:P1Maintainers onlyMaintainers onlyscope:in-focusFeeds the ninety-day committed outcome. Maintainers onlyFeeds the ninety-day committed outcome. Maintainers onlystatus:acceptedIn the backlog. Maintainers onlyIn the backlog. Maintainers onlytype:refimplReference implementation or adapter workReference implementation or adapter workworkstream:coding-agentsOwning workstream. Maintainers onlyOwning workstream. Maintainers only
Type
Projects
- StatusShow more project fieldsIn progress
Target runtime or language
Codex CLI, as a
PreToolUsehook adapter underadapters/codex/What this proves
That a Codex tool call can go to a Guardian as a signed
steps/toolCallRequest, and that the Guardian's allow, deny, and supported parameter overrides come back as Codex's own hook decisions. This is the tool-call part of #89. Tool results, lifecycle events, hosted tools, and ASK/DEFER approval flows are still open under #89.Do you intend to implement this yourself
No, I am proposing it for someone else
Filed by a maintainer so PR #162 has a narrow issue to close. @Lrd0036 wrote the work. This is a sub-issue of #89, which stays open for the rest of the Codex coverage.
Current Priority Scope
Feeds the runnable Guardian reference implementation