[email protected]andClaude Opus 4.6 212fe9817a fix(engine): resolve tool names as callable stubs in CodeAct runtime ...

When LLM-generated code calls `mission_list()` or any tool function,
Monty's Python execution model first resolves the name (`mission_list`)
as a NameLookup before invoking it as a FunctionCall. The NameLookup
handler always returned Undefined, causing NameError before the function
call could dispatch to the effect executor.

Fix: before starting the Monty VM, collect all known tool names from
the effect executor's available_actions(). In the NameLookup handler,
if the name matches a known tool, return a MontyObject::Function stub
instead of Undefined. Monty then yields FunctionCall for the stub,
which dispatches to the normal tool execution pipeline.

This enables CodeAct code to call any registered tool as a Python
function: mission_list(), mission_create(), routine_list(), web_search(),
memory_search(), etc. — all without explicit imports or __execute_action__
boilerplate.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

2026-03-26 23:54:33 -07:00

..

ironclaw_common

feat(engine): complete v2 side-by-side integration with gateway API

2026-03-26 18:19:10 -07:00

ironclaw_engine

fix(engine): resolve tool names as callable stubs in CodeAct runtime

2026-03-26 23:54:33 -07:00

ironclaw_safety

Merge remote-tracking branch 'origin/staging' into v2-architecture

2026-03-26 14:00:35 -07:00