v0.9 · open beta · free while in beta

One quiet desk for everything you almost forgot.

Keyboard-first snippets, boards, and todos — with an API, CLI, and native MCP server, so your agents work the same desk you do.

Get started in 5 minutes → See the four doors

plays well with GitHub · Slack · Claude · Cursor · any MCP client

01 THE DIFFERENTIATOR

One vocabulary, every door.

The same verb, the same permissions, the same audit trail — whether the caller is you, your terminal, your CI, or your agent. Watch the identical move go through all four doors:

cards.move PS-117 → done
Youconsole · ⌘K# focused card, one keystroke → move right · PS-117 → Done
Your terminalqd CLI$ qd cards move PS-117 --status done
Your agentMCPcards.move({ card: "PS-117", status: "done" })
AnythingHTTPPATCH /v1/cards/PS-117 {"workflow_status":"done"}
audit → cards.move PS-117 → done · by Ravi (via Claude) · 09:14 — every write attributed, agents can't self-approve gated moves
02 BUILT FOR AGENTS

The work system your agents already know how to use.

Claude and ChatGPT already plan with checklists, work in sessions, and read schemas. Quietdesk gives those habits a home on the team's record — instead of a scratchpad that vanishes when the session ends.

The agent's checklist lives on the cardin development

The same working todo list Claude keeps internally, persisted via checklist.* — shape-compatible with the model's native habit, so adoption is a one-line skill, not an integration. Watch the plan tick over live; convert items to real subtasks when a person takes over.

Every session leaves a worklogin development

What the agent planned, decided, and concluded lands as a collapsed timeline on the card it worked — any client, any door, planning sessions included. Not just the ones that end in a git push.

Snippets become a schema registryin development

A json-schema snippet type: the public link is the schema's $id, samples validate against it, and agents pull contracts as typed context with schemas.get — no doc scraping.

Gates stay humandesigned in

Agents prepare, people decide. A gated move from an agent is refused on every door — 403 gated_move_requires_human — and every write is attributed: by Ravi (via Claude).

03 HOW IT WORKS
capture

Press N. It's saved before you lose it.

A snippet, a todo, a card — from anywhere. Saving a snippet puts its public link straight on your clipboard: paste code, hit save, share. Versioned from v.01.

move

Boards that read your branches.

Name a branch feat/PS-204-… and the PR links itself to the card. Reviews and merges move it. Subtasks assigned to a person appear in their Today list — one commitment list, no duplication.

finish

Done means done. We check.

Acceptance criteria are counted separately from card status — a moved card with unchecked boxes is not done, and Quietdesk says so. Gated approvals stay human-only; agents prepare, people decide.

04 THE SPEC SHEET

Small surface. Sharp tools.

▸Snippets
HTML · SQL · JSON · plain — versioned, sandboxed HTML preview, one revocable public link each. qd.sk/s/…
▸Boards
Kanban + list views, labels, due dates, blocked states — PRs linked by branch name, moves automated by merges.
▸Today
Personal commitments with priorities and org tags. Card subtasks mirror in; completing either side completes both.
▸Home & Inbox
A read-only action queue of what's waiting on you, and an inbox where every item has one obvious next action. Event noise stays out.
▸⌘K everywhere
Jump, create, act. G then B for boards, N to capture — 100% keyboard-driveable.
▸Milestones
Sprints and deadlines across boards with honest criteria counting. Closed honestly, not quietly.
▸API · CLI · MCP
The full vocabulary on every door — bearer tokens, idempotency keys, cursor pagination. Docs ship as llms.txt.
▸Agent-native
Card checklists agents work natively, auto-captured session worklogs, a JSON-Schema registry, board context packs — plus a Claude Code skill and ChatGPT app. in development
▸PWA
Installable, offline shell, mobile companion for triage: Home, Today, Inbox, Search, card detail.
05 WHY "QUIET"

Boring guarantees, on purpose. Every read and write is scoped to your organization at the service layer. Every mutation writes an attributed audit event in the same transaction. Auth is passwordless — Google, GitHub, magic links, passkeys — with TOTP on top.

No notification confetti, no engagement loops, no dark patterns, no ads. The product's job is to give you your list and get out of the way — and to extend the same courtesy to your agents.

— free while in beta · pricing announced here before anything changes

06 FAIR QUESTIONS
What is Quietdesk?
A keyboard-first workspace for three things teams actually lose: code snippets (versioned, shareable by public link), kanban boards linked to GitHub PRs, and personal todos that follow board cards. One vocabulary across the UI, CLI, MCP, and HTTP API.
How do AI agents use Quietdesk?
Through a native MCP server exposing the same verbs as the UI and CLI (cards.move, snippets.create, todos.list…). Agents act as the person who connected them, every write is attributed and audited, and gated moves — like approving work into Done — stay human-only. In development: agents keep their working checklist on the card, their session worklog is captured automatically, and snippets double as a JSON-Schema registry they can pull typed contracts from.
Is my data isolated per organization?
Yes. Every read and write is scoped to your organization at the service layer. Snippets are private or team-visible; public links expose exactly one snippet, are revocable, and return 404 after deletion.
Why is there no password?
Quietdesk is passwordless: Google, GitHub, magic links, and passkeys, with TOTP two-factor. Your first sign-in creates your account; there is no password to phish, reuse, or leak.
Does it work on mobile or offline?
Quietdesk installs as a PWA. The mobile companion focuses on triage: Home, Today, Inbox, Search, and card detail, with boards rendered as status-grouped lists.
What does it cost?
Quietdesk is in open beta and free while in beta. Pricing will be announced on this site before anything changes.

Start with the thing you keep meaning to do.

Five minutes from the quickstart to your first snippet — public link included.

Read the quickstart → Browse the glossary