What happened
When a session runs in Code Mode, Runtime replaces the normal provider-visible tool surface with its generated exec tool. Safe-boundary resume currently rebuilds available names from the ordinary Host composer, which omits exec. The planner then parks an otherwise-safe continuation with tool_catalog_mismatch after a completed exec call.
This is a separate instance of the generated-tool catalog mismatch fixed for tool_search in #5872.
How to reproduce
- Enable Code Mode for a session.
- Let the model complete an
exec call and commit its response.
- Stop the turn at an otherwise-safe boundary and request resume.
- Inspect the continuation-plan diagnostics for the missing
exec tool.
Expected: resume validation uses the effective Code Mode tool surface, including Runtime-generated exec, and accepts the continuation when the remaining safety checks pass.
Environment
- Maka branch:
main
- Surface: TUI / Runtime Host
- Runtime mode: Code Mode
What happened
When a session runs in Code Mode, Runtime replaces the normal provider-visible tool surface with its generated
exectool. Safe-boundary resume currently rebuilds available names from the ordinary Host composer, which omitsexec. The planner then parks an otherwise-safe continuation withtool_catalog_mismatchafter a completedexeccall.This is a separate instance of the generated-tool catalog mismatch fixed for
tool_searchin #5872.How to reproduce
execcall and commit its response.exectool.Expected: resume validation uses the effective Code Mode tool surface, including Runtime-generated
exec, and accepts the continuation when the remaining safety checks pass.Environment
main