A local board. Inside Codex.

Many chats.
One clear plan.

Give each card a goal, hand it to a chat, and bring the work back for review. Threadboard keeps the whole project in view.

Open source · No board account · Stored locally

Threadboard INTERACTIVE DEMO
Open full demo
Try it: open a card, move it, or make a new task.Example projects. Changes stay in this tab.

01Know what’s next. Goals, priorities, and prerequisites live on the card.

02Know who has it. A claim gives one chat ownership of the task.

03Know what came back. Results wait in Review until you make the call.

THE HANDOFF, WITHOUT THE HUNT

A task can outlive
the chat that started it.

Keep the brief, the owner, and the result in one place. Here’s the path of one installation task.

Start a new chat from a card, or ask an existing chat to pick it up. A new chat opens with a prepared prompt; send it to begin.

TB-7 / PRODUCTReady

Package a one-command installation

Bundle the board, local server, workflow skill, and licenses. An existing installation must keep its cards.

ACCEPTANCE CRITERIA
  • Package versions agree.
  • A clean Codex profile opens the board.
  • Upgrading preserves existing tasks.
No owner yet

The brief is ready for a chat to pick up.

The card keeps the outcome and acceptance criteria together, so the next chat starts with a useful brief.

ILLUSTRATED HANDOFF / EXAMPLE TASK
THE RESULT HAS A HOME
Your review
is a real step.

A FINISHED CHAT ISN’T THE FINISH LINE

Read the result.
Make the call.

A chat submits its work with a short progress note and the checks it ran. You can see the brief and the result together.

Accept into Done↩ Request changes

Threadboard moves on deliberate task updates. It doesn’t read your conversation history or guess whether a chat is finished.

Read the workflow guide

PROJECT FIRST, BOARD SECOND

Your projects.
Room for every kind of work.

Threadboard uses the projects you already created in Codex. Each gets an empty General board. Add Product, Release, or a board for the next thing you want to ship.

One overview. Multiple boards per project.
OrbitCODEX PROJECT
General Start here Product Features & fixes Release Ready to ship

Separate boards.
The same project context.

SMALL FOOTPRINT. CLEAR BOUNDARIES.

The board lives
on your machine.

No hosted board service. No board account. Your tasks live in a local SQLite database, separate from the replaceable plugin files.

YOUR DEVICE
CodexYour projects & chats
task tools
ThreadboardLocal MCP server
read / write
Your boardsSQLite on disk
Threadboard stores task content, chat references, and deliberate updates. It does not open transcript files. Task information you choose to use in a chat still goes through your normal Codex account and model service.
↻

Changes without the churn.

A visible board checks a small local revision once a second. Cards reload after a change. Hidden panels pause, and open drafts stay open.

↗

Your work survives updates.

Plugin files and task data have separate homes. Export a readable JSON snapshot, or back up the database to keep a restorable copy.

⌘

Built for your workspace.

Use the keyboard, work in a narrow panel, and follow your Codex theme. Threadboard stays beside the chats doing the work.

BEFORE YOU INSTALL

A few good questions.

Threadboard is an open-source preview. Here’s what it does today.

What do I need?

Codex desktop with plugin and MCP App support, the Codex CLI, and Node.js 22.13 or newer. The package includes the compiled app, so you don’t need npm or a build step to use it.

Will a card start a chat automatically?

Start in new chat opens Codex with a prepared task prompt. Send it to begin. You can also ask an existing chat to claim a card. A claim gives one chat ownership; it does not quietly dispatch model turns in the background.

What gets sent to a server?

Threadboard has no hosted backend and doesn’t sync boards or transcripts. When you ask Codex to work on a task, that task context uses your normal Codex model service and allowance. Local storage doesn’t make the model run offline.

Can I use it across multiple computers?

The current preview is for one device. It has local exports and database backups; it has no account or cross-device synchronization.

How ready is the preview?

Board opening has been confirmed in Codex. Backend, browser, performance, and installation checks run in CI. Native chat placement and full-view navigation recovery are still experimental. Read the current release notes.

Does it cost anything?

Threadboard is free and MIT licensed, with no board subscription or hosted backend to pay for. Task work still uses your existing Codex account and model allowance.

MAKE ROOM FOR YOUR NEXT TASK

Put a board
behind the work.

Install the preview. Open Threadboard in Codex. Your projects are already waiting.

Download the preview 1.2 MB

v0.1.4-dev.7 · Node.js 22.13+ · Codex CLI

Verify the checksum
  1. 01

    Extract the ZIP and open a terminal in that folder.

  2. 02

    Run the installer.

    node install.mjs
  3. 03

    Fully quit and reopen Codex. Open Threadboard from the sidebar.

Already have boards? The installer keeps your task data. User guide ↗

Built in the open.

Read the code, try the preview, or help decide what comes next.

Explore the repository
Threadboard
Actual interface / example projectsOpen original ↗