thread-homebase
Thread homebase
Use the Codex task registry and recent task content to identify current work and unresolved commitments. Do not reconstruct repository delivery status from a coordination task.
Find the work
Include active tasks and the 6–12 most recently updated non-archived Codex tasks. Broaden the search when the user asks for older or forgotten work.
Start with registry titles and summaries. Read recent turns when ownership, completion, or the next action is unclear. Prefer the latest user steer and unfinished assistant commitment over the original task premise. idle or not loaded does not mean completed; report only what the evidence supports.
Identify the smallest owner of the current decision or deliverable. For ordinary repository work, use the working directory as a starting point. A routing workspace such as Workspaces is not itself the project: infer the owner from task content. Preserve cross-project or unresolved ownership when a single repository would be misleading. Distinguish the owner from other repositories merely discussed or affected.
Report
Put active work first, then group tasks by project or owner. Give each group a ## <project or owner> header, with a blank line between groups. Do not repeat the project on every task line.
Use short lines:
[Exact task title](codex://threads/<thread-id>) — <current work or open question; explicit PR # or Linear code when available> — <status>