process · persist-pseudo-code-plan-restrict-calls TEC-0156 · proposed

Persist a pseudo-code plan and restrict calls to it

Before any action, the agent generates an ordered pseudo-code sequence of tool calls, writes it to a scratchpad that persists across the whole episode, and the executor admits only the plan-specified tool at each step unless replanning is t

Proposed. Filed by the drafting stage because a paper introduces or tests it. Nobody has vouched for it. The claim drafted from that paper is its first evidence, and what the paper used to validate it is in that claim’s source note. Say whether it held up for you, below.

Before any action, the agent generates an ordered pseudo-code sequence of tool calls, writes it to a scratchpad that persists across the whole episode, and the executor admits only the plan-specified tool at each step unless replanning is t Filed by the drafting stage from Bridging Thought and Action: Taming Long-Horizon Instability in Open-Source LLM Agents with a MetaTool-Enhanced ROS Framework (2609.13335) with status proposed: the paper introduces or tests it, and the claim drafted from the paper is its first evidence. The paper validated it by: Four-configuration ablation (prompt only, transient plan, persistent plan, persistent plan plus execution constraint) over three task tiers and four models, 20 trials each; 40 hardware trials comparing repeated tool calls (19.0% to 6.1%), invalid calls (21.7% to 8.1%) and execution time against vanilla ROSA; and a 40-trial failure-mode comparison against re-implemented ReAct (17/40 success), CaP (20/40), ROSA (23/40) and MetaTool (30/40).. Nobody has vouched for it; add support or contest it on this page.

Addresses: Completing tasks that take many steps or many hours

Does it work?

nothing measured0 supporting · 0 contesting sources

Efficacy claims — what this technique actually moves, under which conditions, and whether that has been contested.

No efficacy claim filed yet. The technique is catalogued; whether it moves the capability, and when, is a separate assertion that needs its own sources.

No search recorded either, so this says nothing about the literature — only that nobody has looked here yet.

Code

No repository linked yet. Contribute one.

Sources

Either way, bring evidence: a link, or what you saw.

Whether a technique works is a claim. What you file here becomes a claim about this technique under the capability it addresses, with your evidence as its source, and moves the standing above the same way a paper would.