Pi-Goal

Pi-Goal brings Codex-style long-running goals to pi. It keeps a thread objective moving across turns, auto-compaction, provider errors, and queued user messages while preserving user control with /goal pause, /goal resume, and /goal clear.

Install and How to Use

pi install npm:@kky42/pi-goal

Use /goal [<objective>|pause|resume|clear] from any pi session:

• /goal shows the current goal.
• /goal <objective> creates or replaces the active thread goal and sends the agent a visible goal-wrapper message.
• /goal pause pauses the current goal.
• /goal resume resumes a paused or blocked goal.
• /goal clear clears the current goal.

update_goal is the only goal tool; the same goal wrapper is used for starts, resumes, and continuations.

Model-facing wrapper shape:

<goal>
<objective>
...
</objective>
<instructions>
You are working on this active goal.
...
</instructions>
</goal>

Pi-Goal vs. Codex Goal

Area	Pi-Goal	Codex Goal
Availability	Installable pi package: pi install npm:@kky42/pi-goal	Built into Codex
Goal start	/goal <objective> stores a thread-scoped goal and sends a visible wrapper follow-up	Native goal initialization in the Codex thread
Continuation	Scheduler-owned visible custom follow-ups after idle; queued user messages win	Native Codex continuation loop
State	Stored in pi session entries for the current session tree	Stored in Codex's internal thread goal state
Completion	Agent marks complete via update_goal from the active wrapper contract	Same completion-audit contract
Blocked state	Agent can mark blocked; /goal resume reactivates paused or blocked goals	Same blocked/resume behavior
Prompting	No always-on goal system prompt; no hidden active-goal context	Managed by Codex internals
Main difference	Codex-style goal behavior implemented as an inspectable pi extension	First-party Codex implementation