Keep Codex threads and quota in view.

Follow the turn, then review the result

Codex session logs and hooks supply different parts of the picture. Task cards group sessions by observed status so you can find a turn that needs attention, a turn still running, or a reply ready for review. Filter by project or time range instead of reopening every conversation.

A Replied state means the turn ended. It does not certify that generated code works or that the task passed review. Open the specific Codex thread to inspect the output and continue there.

Read account quota alongside local usage

Codex supports official quota readings as well as local records. These answer different questions: subscription windows describe account capacity, while task token counts describe observed work. Check the source and reading time before making a decision.

Account quota is shared across sessions. VibeBoard keeps the newest account reading rather than adding a separate allowance for each thread. An expired credential or failed request should explain why a reading is unavailable.

Check hooks with a short Codex task

In VibeBoard’s Agents view, review the detected Codex source and install the supported hooks. Codex may require you to approve hook trust in its own interface. Run a short task and confirm that the last event time changes before relying on status updates.

Try this workflow on your Mac

Use the 3-day trial to check Codex support with your own tools before choosing a one-time license for 1, 2, or 3 Macs. Waffo hosts checkout. Third-party AI subscriptions and model costs are separate.

Start a free 3-day trial once per physical Mac, or paste your license key during onboarding or in Settings → License. No account or card is needed for the trial. Paid licenses renew a signed 30-day receipt online about once a month.