Clarify code execution status handling
Treat trailing framework status as execution guidance rather than command output, preserving correct wait, reset, rerun, and continuation decisions.
Alessandro committed
Jul 16, 2026 at 19:44 UTC
d3bec80611a88da85bc898567c26a89046095d35
1 file changed
+1
-1
plugins/_code_execution/prompts/agent.system.tool.code_exe.md
+1
-1
@@ -14,7 +14,7 @@ rules:
14
- replace placeholder or demo data with real values before execution
15
- use `print()` or `console.log()` when you need explicit output
16
- do not interleave other tools while waiting
17
-- ignore framework `[SYSTEM: ...]` info in output
17
+- treat trailing framework `[SYSTEM: ...]` info as execution status, not command output; use it to decide whether to wait, reset, rerun, or continue
18
- probe cwd files tools and dependencies before expensive commands
19
- split long work into small commands: inspect, prepare, run, verify
20
- for builds installs servers training and long tests, redirect logs and poll with `runtime=output`