ThreadBear keeps Codex Desktop task titles useful in the turn that is doing the work. Managed guidance asks each ordinary turn to make two native title calls: one before work starts and one immediately before the final status footer. Two small hooks preserve the task's user-owned subject and expand those compact calls into the visible title.
| Mark | Meaning |
|---|---|
| ⏳ | running |
| 🚨 | blocked |
| 🙋 | needs input |
| 🤖 | healthy automation |
| ➡️ | next steps |
| ✅ | complete |
| ❔ | unknown legacy state |
The canonical shape is <mark> <subject>[ → <action>]. ThreadBear owns only decoration it previously committed. User renames are adopted intact, and every rendered title is bounded to Codex Desktop's 60 UTF-16-unit limit.
Open INSTALL.md in a new Codex task and follow the guided preview, consent, persistent-home setup, controller migration, and rendered Desktop verification.
ThreadBear installs a standalone Go binary, one small private state file, managed guidance, and two Codex hooks. The initiating task becomes the persistent 🧵🐻 ThreadBear 🐻🧵 home; one ephemeral controller owns installation migration so that home returns promptly.
threadbear install
threadbear inventory
threadbear migration
threadbear status
threadbear self-test
threadbear uninstall
threadbear version
Every command accepts --json. inventory is read-only and includes every local unarchived task across source shapes, including projectless tasks, excluding the persisted main and controller tasks. status reports ready:true only after migration_complete; the installed binary's help output is authoritative.
ThreadBear does not install a daemon, schedule heartbeats, archive ordinary tasks, add token counts, update itself in the background, or edit Codex private UI storage. It adds no model call or narration to ordinary turns. Installation uses one serial native-writing controller and at most eight ephemeral Luna-medium workers only when genuinely ambiguous history cannot be classified deterministically; those workers classify and never write titles.
See architecture, compatibility, and the status footer convention.