Skip to content

Introduction

Quietdesk is a keyboard-first workspace for three things teams actually lose:

  • Snippets — versioned code fragments (HTML, SQL, JSON, plain) with one revocable public link each. Saving copies the link to your clipboard.
  • Boards — kanban wired to GitHub: branch names like feat/PS-204-… auto-link PRs; reviews and merges move cards.
  • Todos ("Today") — one personal commitment list. A subtask assigned to you on a card appears in your Today list, still visibly linked to its card.

Around them sit a personal Home (what's waiting on you, with the next action attached), an action-first Inbox, Milestones that count acceptance criteria separately from card status, and ⌘K everywhere.

The one idea that matters

One vocabulary, every door. The UI, the qd CLI, the MCP server, and the HTTP API all speak the same verbs:

DoorMove a card to Done
UIdrag, or with the card focused
CLIqd cards move PS-117 --status done
MCPcards.move({ card: "PS-117", status: "done" })
HTTPPATCH /v1/cards/PS-117 {"workflow_status":"done"}

Every call is scoped to your organization, checked against your role, and written to the audit log with full attribution — by Ravi (via Claude) is a first-class actor.

Agents, with gates

Agents connect via MCP with a personal token and act as the person who connected them. Read tools are safe by default; write tools require a write-scoped token. Gated moves — approving work into done on gated boards — are rejected for agent callers with 403 gated_move_requires_human. Nothing self-approves.

Where to go next

  1. Quickstart — first snippet, public link included, in five minutes.
  2. Glossary & data model — the canonical dictionary; agents should read this first.
  3. API guide — auth, errors, pagination, idempotency.
  4. Availability & roadmap — what's live in the beta, with status badges.

One vocabulary, every door.