-
Notifications
You must be signed in to change notification settings - Fork 3
plat 441
github-actions[bot] edited this page Oct 4, 2026
·
2 revisions
| Coordination | Value |
|---|---|
| State | fixed on main; not deployed |
| Date | 2026-10-04 |
| Owner | plans-contracts |
| Related | PLAT-432 (scripted routes as named tools), PLAT-423 (retired Python tools), PLAT-431 |
- Relay agents may call saved Python scripts as tools (scripted routes). No sub-agents in Relays.
- Relays have no workflow database, knowledge base or learnings.
Both "no routes on a Relay agent" rules came with the Relay MVP (2026-09-27)
without a recorded reason. In code: an agent with routes runs on the delegation
runtime, and delegatingMessageSequenceAsOrchestrator dropped authored_prompt
and system_prompt, so a Relay agent with routes would have lost its prompt and
JSON result contract.
-
OrchestratorPlanStepcarriesAuthoredPrompt/SystemPrompt(runtime only) through the conversion, so the sequence executor keeps the authored prompt, the authored items and the JSON result check. The authored prompt is used verbatim plus an appended "Tools and sub-agents of this agent" block. - An authored agent gets no generic delegation tools or executors
(
call_sub_agent,call_generic_agent, query/stop): only its named script tools. - Plan validation no longer forbids routes on an authored agent. Relay validation
allows only
type: regular,script_only: trueroutes; sub-agents are refused. Publishing requires each route's savedcode/<route>/main.py. - Relays skip the knowledge-base and managed-DB migrations; the four DB tools PLAT-431 gave the Relay Builder (never deployed) are removed.
- Relay Builder prompt and skill describe script tools (no sub-agents, no workflow DB/KB/learnings; user systems via secrets).
- Tests: Relay validation, authored prompt surviving delegation, the tools block,
Relay migration plan.
cli-step-contractruns an authored agent that calls its script tool and answers JSON with the script's value.
- Runtime DB/KB/learnings removal was approved by the owner and implemented in PLAT-447. Deployment and live verification are tracked there.
Auto-synced from docs/ on main. Edit there, not here.