turtle1999
ab2f5d3009
Tool guidance sections keep only what the tool definitions do not say. Apply review: reword interrupt_agent and list_agents, carry "a rejected escalation stays denied" in the rejection error, pin sandboxPermissionsDescription, and fix stale README and Agent Note statements. Record the tool-definition rules in agent-experience. Compaction threshold snapshots shift their context windows by the 370-token system-prompt estimate reduction; escalation-rejected moves to a v4 fixture for the new rejection text.
description, kind
| description | kind |
|---|---|
| The todo group map: the model-facing todo_write tool over the session log, for users and maintainers navigating the group. | package-group |
packages/todo
English | 中文
Summary
The todo group gives agents a session-level task list to plan with: add tasks, mark them in progress, and check them off, with the same list persisting across turns and reopened sessions. It is one product package that provides the todo_write tool; the list belongs to the agent session that created it, and each update replaces the whole list. Interactive hosts show the standing plan from the list, while the group itself ships no UI.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
tool-todo |
Lets the agent maintain a session task list: plan tasks, update status, and track progress | registers on ctx.tools |
Related documentation
- Todo subsystem — the
todo/writeevent payload, ownership rules, andTodoItem. - Generated tool catalog — the
todo_writeschema the model receives. - Generated configuration catalog — every accepted config field.
- todo_write tool Agent Note — the original design and its alternatives.
Dev Note
Working context for maintainers — click to expand
None.