Frequently asked questions

TaskChef is for people who use Codex throughout the day and have several projects or chats in progress. That includes developers building features, maintainers investigating bugs, and people working on multiple side projects.

If you often switch between chats to check progress, review a result, or find a PR that is ready to merge, the board gives you a shared view of that work. You can also use it for several parallel chats within one project.

Connecting GitHub is highly recommended. It shows live PR and CI status and automates the Done workflow: TaskChef can move a chat to Done once all PRs from its latest completed turn are merged.

Your local chats appear without GitHub access. For work across organizations, grant TaskChef access in each organization you use.

Each organization controls its own GitHub app installation and repository access. Permission granted in one organization does not grant access to the others.

Use Manage repository access, select each organization you work in, and install or configure TaskChef for its repositories. An organization owner may need to approve access.

The current TaskChef package needs compatible Node.js and npm. Codex uses npm to download TaskChef, and Node.js runs its local MCP server. The server dependencies are already included in the package.

Supported versions are Node.js 22.18+ in the 22 series, or 23.2 and newer. Node.js 24 is recommended for a new installation. See the installation guide.

No. TaskChef estimates the equivalent API cost of the recorded usage. This helps you compare the latest turn with the whole chat; it is not a charge against your Codex subscription.

The estimate can be incomplete when usage records or model prices are missing. TaskChef labels incomplete estimates in the usage panel.

A finished turn is ready for you to review its result. It may still have a PR to merge or work that you want to continue.

• Work with PRs: merge the PRs. With GitHub connected, TaskChef can move the chat to Done once all latest-turn PRs are confirmed merged.
• Finished work without PRs: use Mark Done in Details, or drag the card to Done. This is available for finished chats without an active schedule.
• Work you want to put away: archive the chat in Codex. Archived chats are hidden by default; enable Show archived chats in TaskChef settings to see them.

Chats with an unmerged PR cannot be manually moved to Done. Completed scheduled runs return to Scheduled.

No. You can use the board and start chats through Codex as usual.

$taskchef:delegate is an optional tool for a master-chat workflow. Keep one chat where you describe jobs, then let the skill find the right project and start each job in a new native Codex chat. You can follow those chats on the board and open them when they need attention.

The skill can remember project aliases and routing preferences you confirm. Those hints can help it route familiar bug links or keywords with less input over time. It asks when the project is unclear. See the delegate guide.

In Codex’s plugin settings, refresh the marketplace that provides TaskChef, then install the available update. Restart Codex after updating the plugin so its local server loads the new release.