packages/goal
September 6, 2026 · View on GitHub
English | 中文
Summary
The goal group gives an agent session one durable completion objective that survives restarts, resume, and fork: the goal service keeps the goal state and lifecycle durable, the model tools let the agent create and update goals, the /goal command gives the human direct goal control without a model turn, and the continuation driver turns an active goal into sequential rounds of automatic work. Goal state lives in the session log, so nothing in the group keeps a separate store. Only one goal is current at a time, and a goal is state, not a scheduler — automatic continuation is an opt-in consumer you mount deliberately.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
goal | One durable goal per session: create, edit, pause, resume, complete, block, and clear | ctx.goals |
tool-goal | Model tools get_goal, create_goal, update_goal | registers on ctx.tools |
command-goal | Human /goal command in UI command planes | registers on ctx.commands |
goal-round-driver | Automatic continuation: turns an active goal into sequential rounds | no service key |
Related documentation
- Goal subsystem — goal types, durable
goal/changeevents, and the generated service API. - Generated tool catalog — the three goal-tool schemas the model receives.
- Generated configuration catalog — every accepted config field of the goal service.
- Goal domain Agent Note — the domain design and its decisions.
- Same-session driver Agent Note — the continuation races and lifecycle rationale.
Dev Note
Working context for maintainers — click to expand
None.