I’m building a task board for Codex. I’ll share it with the community first once it’s done.
You can think of newtype-task as: task management and acceptance live in newtype-task, while the actual coding execution still happens in the official Codex App.
newtype-task is not an unattended system where you create a batch of tasks and background agents automatically pick up all of them to execute. The current design deliberately keeps two manual checkpoints: 1. before execution starts, the user confirms sending it to Codex. 2. after Codex delivers, the user reviews it and decides whether to mark it complete.
The reason for keeping these manual checkpoints is to reorganize the work scattered across different Threads in the Codex App into tasks that can be managed, tracked, and accepted.
When there are only a few tasks, just opening Threads in Codex is perfectly sufficient. But once there are many tasks, you usually run into problems like: not remembering which ones have started and which haven’t; Thread titles failing to accurately reflect delivery status; not knowing which task is blocked; and so on.
The role of newtype-task is to downgrade Threads from “work management objects” back to “execution records.”