Where Claude Code and Codex keep /goal state, and how one open-source app reads both
Both Claude Code and Codex now have /goal : you give a session a condition that can be checked, and the agent keeps working round after round until the condition is met. It is a good fit for long, well-defined jobs such as "get every unit test passing" or "first paint under 1.5 s and Lighthouse above 90", the kind of task where an agent would otherwise stop halfway and write a confident summary.…
Both Claude Code and Codex now have the ability to set goals for long, well-defined tasks. Claude Code records goals in JSONL transcript attachments, while Codex stores goals in a SQLite database. An open-source app called Kiteline can read both formats and present a unified view of goal progress. Kiteline uses a small state machine to track goal states, and prefers explicit signals like pause markers before concluding a goal is stopped. The app caches data from Codex to avoid competing with the database for write locks.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
