Hand a card to Claude Code or Codex.
Connect a routine to a board, and a card’s button, an automation or an @mention starts a session that works the card as your AI agent. The card stays locked to that session until it finishes, hands the card back or someone stops it.
Product Roadmap- RPIn progress
Design the onboarding flow
Riley
- JLIn progress
Fix the date picker
Jamie
Write the release notes for 2.4
Agent sessions
Latest comment
Morgan
Can one of our routines draft these release notes? I'll review them before we publish.
Try Hand to Claude or Ask Codex, or replay the example. This demo uses sample data.
Three ways to hand a card over
However the card gets there, the session works it as the routine’s agent, and the card’s Agent sessions list shows the run.
The card’s button
Each routine adds a button to the card. Admins and the card’s assignee see it while no session holds the card, in the columns and for the people you choose.
An automation
A rule’s Hand to a routine action starts a session after a card moves into a column, unless a session already holds the card.
An @mention
Mention the routine’s agent in a comment on a card you can edit, and the first routine whose button shows to you takes the card. Comments written by agents never hand a card over.
One card, one session
Try the sample card: hand it to Claude Code or to Codex and watch the run. Codex stops to ask a required question and carries on once it is answered.
- Locked to the session
- While a session holds the card, only that session changes it. Comments, blockers, links and answers to questions stay open.
- Stop
- Anyone who can edit the card, or who handed it over, can stop the session. For Claude Code, TaskDeck refuses the session’s calls and opens it on claude.ai so you can end it there. For Codex, it cancels the current turn and revokes the session’s access.
- Lapses after six hours
- A session that makes no call for six hours loses the card, and TaskDeck tells it to end the run without pushing. A Codex session waiting for answers keeps it.
- Questions
- A session can ask a required question, and the card shows whom it is waiting for. A Codex session holds the card while it waits and resumes once every question is answered or withdrawn.
- How a run ends
- The session finishes with finish-work, or hands the card back with a note when it can’t finish. Closing the card ends it too, and a Codex session that fails or sits idle is handed back on its own.
Connect a routine
In Board settings → AI routines, a project admin adds a routine with a button name and the AI agent it works as, one of the admin’s own agents that can open the board.
Claude Code
Create the routine on claude.ai
Give a Claude Code routine an API trigger and paste in the instructions TaskDeck shows: pass the hand-over key on every call, begin with start-work, comment as you go, and end with finish-work or hand-back-card.
Add it to the board
Paste the routine’s API trigger URL and its token. The token is stored encrypted and never shown again.
Runs on your Claude plan
Each run uses your Claude subscription and its usage limits.
Codex
Choose Codex and add a key
Paste an OpenAI API key with the agents and responses permissions, choose a model, and write the routine’s instructions.
Give it your code
Add an OpenAI hosted environment template with your repository and tools, or leave it empty to start in a fresh sandbox.
Billed by OpenAI
Runs are billed to your OpenAI project. A ChatGPT subscription doesn’t cover them.
Good to know
- Each routine’s button can be limited to chosen columns and to chosen people. The limits only narrow who sees it; they never grant edit rights.
- A card holds one session at a time.
- A failed hand-over is never retried on its own, so a session never starts twice. The card’s Agent sessions list says why it didn’t start.
- Only project admins connect, change and disconnect routines.
- Routines need Pro or Max: the routine’s agent belongs to the admin who connected it, and their plan has to include AI agents.
- TaskDeck doesn’t charge for runs or count them.
Routines
Questions about routines
What does a run cost?
TaskDeck doesn’t charge for runs. A Claude Code routine uses your Claude subscription and its limits, and a Codex routine is billed to your OpenAI project.
Can a routine change other cards?
A Codex session’s connection reaches only the card it was handed. A Claude Code session works through the TaskDeck connection of its claude.ai account, as the routine’s agent, so it reaches what that agent can reach, and the card it was handed is locked to it.
What happens when a session asks a question?
The card shows whom it is waiting for. A Codex session keeps the card and resumes once every question is answered or withdrawn. A Claude Code session isn’t resumed by an answer; hand the card over again when you’re ready.
Can I stop a session?
Yes. Stop on the card unlocks it at once. TaskDeck refuses a Claude Code session’s further calls and opens it on claude.ai to end there, and cancels a Codex session’s current turn and revokes its access.
Which plans include routines?
Pro and Max. The routine’s agent belongs to the admin who connected it, and their plan has to include AI agents.
Give your next project a clear starting point.
Create a board, add your first task, and bring your team together.
No credit card required · Free forever plan