This chapter explains what Taskdeck is for and how to get to first value quickly.
Taskdeck helps you move from messy input to explicit, reviewable work.
The core promise is simple:
- capture something fast
- shape it into a proposal
- review the change before it lands
- continue the real work on a board
Taskdeck is not trying to hide automation behind silent mutation. The review step is part of the product, not a temporary limitation.
- open
Home - create or open a useful board
- put one note or task into
Inbox - run
Start Triage - open
Review - approve and execute one proposal
- continue from the board
If you only do one thing on your first run, do that loop once.
Home
- the default landing page and reset surface
Today
- the agenda view for review, triage, and due or blocked board work
Inbox
- where rough notes, pasted text, follow-ups, and transcripts wait to be shaped
Review
- the trust gate where proposals stop before they touch a board
Boards
- the shipped label for workspaces where cards live
Projects
- the product-facing term that may appear in docs or later UI language for the same board concept
Queue
- an advanced manual automation input surface, not the normal first-run path
Agents
- future-facing supervised assistant surfaces that are not part of the shipped shell yet
Shipped and part of the normal path:
HomeTodayInboxReviewBoards
Shipped but usually advanced:
ChatActivityNotificationsOpsAccessArchive
Planned, not shipped:
AgentsRunsKnowledgeIntegrations
From frontend/taskdeck-web:
npm run demo:seedUse the seeded workspace when:
- you want real examples immediately
- you are evaluating the product rather than starting empty
- you need a walkthrough or training baseline
- starting from
Queueinstead ofInbox - thinking
Reviewis optional - expecting
AgentsorIntegrationsto be current top-level workspace pages - reading
Projectsin docs as a different concept from the currentBoardslabel