open beta · free while in beta

The shared work desk for PMs, developers, and AI agents.

Quietdesk keeps product cards, todos, snippets, acceptance criteria, PRs, and agent worklogs in one auditable workspace — accessible from the UI, CLI, API, and MCP.

PMs write intent. Agents do the legwork. Developers ship. Humans approve.

Agents prepare. Humans decide.

Quietdesk is an agent-native product workspace where PM intent, developer execution, GitHub progress, agent worklogs, and human approvals live on one card.

works with GitHubClaudeCursorChatGPTMCPCLIAPI
the problem

Agent work disappears into chats, terminals, and scratchpads.

Your agent planned well, coded fast, and made three decisions worth remembering — inside a session that's already gone. The spec is in Notion, the ticket in Linear, the debate in Slack, the PR in GitHub. Nobody holds the whole story.

Before
After

One card. The whole story.

  • Intent — what the PM actually wanted
  • Criteria — what “done” has to mean
  • Checklist — the agent's live plan
  • Worklog — what it did, decided, and risked
  • PR — linked by branch name, moved by merge
  • Approval — a human, on the record
  • the quietdesk answer

    One vocabulary. One audit trail. One human gate.

    01 · ONE VOCABULARY

    Same verbs, everywhere

    cards.move, snippets.create, todos.list — identical in the UI, the CLI, over MCP, and raw HTTP. Agents don't get a dumbed-down API; humans don't get a side channel.

    02 · ONE AUDIT TRAIL

    Every write attributed

    Human or agent, every mutation lands in the audit log with who, what, when, and through which door: by Ravi (via Claude) · 09:14. No invisible work.

    03 · ONE HUMAN GATE

    Approvals stay human

    Gated moves — like approving into Done — are refused for agents on every surface: 403 gated_move_requires_human. Agents prepare, people decide.

    the four doors

    Four doors. One desk.

    One operation — cards.move PS-117 → done — from four different callers. Same permissions, same result, same line in the audit log.

    🧑‍💼PMconsole · ⌘K move right · PS-117 → Done
    👩‍💻Developerqd CLI$ qd cards move PS-117 --status done
    🤖AgentMCPcards.move({ card: "PS-117", status: "done" })
    ⚙️CI / anythingHTTPPATCH /v1/cards/PS-117 {"workflow_status":"done"}

    audit → cards.move PS-117 → done · by Ravi (via Claude) · 09:14 — every write attributed

    for PMs

    You stay the control layer — without the status-chasing.

    Write intent once, let humans and agents execute, and keep the final word. Quietdesk makes “done” something you can verify, not something you have to take on faith.

    🎯
    Criteria live apart from status

    Acceptance criteria are counted separately from the card's column. A moved card with unchecked boxes is not done — and the board says so.

    📋
    Agents work in the open

    Agent checklists are coming next: their plan will be visible on the card while work happens, but they still won't be able to self-approve gated moves.

    🧾
    Every session leaves a worklog

    What the agent planned, changed, tested, and decided lands on the card it worked. You read the receipt, not the chat scroll-back.

    🔗
    PRs link themselves

    Branches named with the card id wire the PR to the card automatically. Review and merge state show up without anyone reporting it.

    🏁
    Milestones don't lie

    Completion is computed from criteria, not from cards that got dragged rightward on a Friday afternoon.

    🔐
    You are the final gate

    Approving work into Done is a human act — on every surface. Every agent attempt at it is refused and recorded.

    for developers

    Name the branch right. Everything else is automatic.

    No status theater. Ship through branches and PRs like you already do — the card keeps itself up to date, and the CLI covers everything the UI does.

    🌱branch feat/PS-204-refund-flow created → card linked9:12 am
    🔃PR #1284 opened → card moved to In review11:40 am
    🧪checks green · review requested → visible on the card1:05 pm
    🎉PR merged → PS-204 → Done · 2 subtasks closed · criteria checked4:58 pm
    $ qd snippets create --type sql -f refund.sql
    ✓ saved as v.01 · ✓ public link copied: qd.sk/s/refund-eligibility-90d
    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: checklists persist on cards, sessions become worklogs, and schemas.get serves typed contracts — no doc scraping. Versioned snippets and revocable public links are live today; the agent layer below is coming next.

    action cards.move PS-204 → done
    caller claude · via MCP · operated by Ravi
    result 403 gated_move_requires_human
    on record attempt logged · waiting on Ravi
    resolution criteria 4/5 · agent approval refused · Ravi approved · 5:02pm

    The one verb agents don't get: approving their own work.

    where things stand

    Live in beta today. Honest about the rest.

    The core workspace is live in beta today. The deeper agent-native layer is landing next — and we'd rather tell you that than pretend.

    Live in beta

  • Boards & cards
  • Acceptance criteria
  • Todos
  • Snippets
  • GitHub-linked cards
  • Milestones
  • API
  • CLI
  • MCP
  • Audit attribution
  • Human-gated moves
  • Coming next

  • Agent checklists on cards
  • Auto-captured worklogs
  • Schema registry
  • Board context packs
  • Claude Code skill
  • ChatGPT app
  • security & trust

    Boring guarantees, on purpose.

    🏢Org-scoped everything

    Every read and write is scoped to your organization at the service layer. No cross-tenant leaks, by construction.

    🧾Attributed audit trail

    Every mutation — human or agent — is logged with who, what, when, and through which door.

    🔐Human-only gates

    Approvals can't be automated away. Gated moves are refused for agents on every surface.

    🔑Passwordless auth

    Google, GitHub, magic links, and passkeys. Nothing to phish, reuse, or leak.

    📱TOTP two-factor

    Standard authenticator-app 2FA on top of passwordless sign-in.

    🔗Revocable public links

    A public link exposes exactly one snippet, can be revoked anytime, and 404s after deletion.

    No notification confetti. No engagement loops. No dark patterns. The product keeps the record straight and gets out of the way — and extends the same courtesy to your agents.

    fair questions

    Asked and answered.

    Is this a Jira / Linear replacement?
    Existing tools track tasks; Quietdesk tracks human + agent execution on one record — intent, criteria, checklists, worklogs, PRs, and approvals. If your agents work outside your tracker today, this is where their work becomes team-visible.
    How do agents use Quietdesk?
    Through a native MCP server exposing the same verbs as the UI and CLI (cards.move, snippets.create…). Agents act as the person who connected them, and every write is attributed and audited. Coming next: checklists on cards, auto-captured worklogs, and a schema registry.
    Can agents approve work?
    No. Gated transitions stay human-only on every surface — the attempt is refused with 403 gated_move_requires_human and recorded. Agents prepare; people decide.
    What works today, and what's still coming?
    In beta now: boards & cards, acceptance criteria, todos, snippets, GitHub-linked cards, milestones, API, CLI, MCP, audit attribution, human-gated moves. Coming next: agent checklists on cards, auto-captured worklogs, the schema registry, board context packs, a Claude Code skill, and a ChatGPT app.
    How does GitHub linking work?
    Name a branch with the card id (feat/PS-204-…) and Quietdesk links the PR, tracks review state, and moves the card on merge.
    Is my data isolated per organization?
    Yes — every read and write is org-scoped at the service layer. Public links expose exactly one snippet, are revocable, and 404 after deletion.
    What does beta pricing mean?
    Free while in beta. Pricing gets announced here before anything changes — no surprises.

    One desk for your team — humans and agents included.

    Five minutes from the quickstart to your first card, criteria and all. Agents welcome at the same desk.