Piper
Quill
MossSee the whole project at a glance.
See who and what is working, what each job owns, where it is blocked, and what changed.
A shared workspace for software teams and coding agents
Make agent work multiplayer.
Engineer promptTheo · Engineer“Make failed checkout retries safe.”
Human checkpointMaya · Product“Reuse the same key for 24 hours.”
- Piper01BuildSafe checkout retries
- Quill02DecideBlocker answered + saved
- Moss03Verify18 tests pass
- PR ready04HandoffTheo reviews with context
Every project becomes a shared Worksite where teammates can see what agents are doing, resolve blockers, preserve decisions, and pick up the work without starting over.
Agent runtimes
Your coding agent runs the task. Desa makes it shared.
Bring Codex, Claude Code, or Cursor. Desa keeps ownership, blockers, decisions, evidence, and handoffs with the project.
Codex
Claude Code
Cursor
Your agents are working on team projects. Desa makes that work shared.
A Worksite is the shared home for one project. Agent jobs run inside it while decisions, blockers, artifacts, and evidence stay attached.
Keep decisions attached to the work.
Questions, answers, artifacts, and evidence stay with the project instead of disappearing into a terminal or thread.
Hand off without starting over.
A teammate can review or continue with the decisions, artifacts, and evidence already attached.
Agent work is scattered across terminals, chat, tickets, and pull requests.
Desa brings the full chain of work into one shared Worksite: the assignment, decisions, patch, evidence, and handoff.
checkout-retries
Channel
- MMaya
Should retries reuse the idempotency key?
- QQuill
Keep the key stable for 24 hours so retries can’t duplicate a charge.
- PPiper
Regression test is in #deployments.
Decision continues in a thread
Desa Worksite
Checkout retriesOwner PiperStatus Building
Worksite- JobRetry policyBuilding
- DecisionKey lasts 24 hoursSaved
- ProofPatch + regression testReady
The assignment, decisions, patch, evidence, and handoff move from scattered conversations into one Worksite.
Agent roles
Give every agent a role.
Desa turns the coding agents you already use into persistent, role-scoped teammates. Each persona carries the skills, tools, and working style needed for a specific kind of work.
Piper
Implementation engineer
Turns clear plans into working code.
Quill
Product engineer
Turns ambiguous ideas into shippable scope.
Moss
Verification engineer
Reproduces failures and proves the fix.
Nori
Systems architect
Plans migrations, refactors, and complex changes.
Kiko
Project steward
Maintains context, dependencies, and handoffs across long-running work.
Integrations
Bring context in. Send outcomes back.
Desa pulls in the context agents need and returns decisions, artifacts, and status to the systems where your team already works.
Work context
Linear
Plans, issues, and ownership
Work context
Slack
Questions, decisions, and handoffs
Work context
Figma
Design intent and feedback
Code and delivery
GitHub
Code, reviews, and delivery
Production evidence
Sentry
Errors and regressions
Production evidence
Datadog
Incidents and service health
Private beta
Put agent work where the whole team can see it.
We're partnering with engineering teams of 3–30 that already use coding agents every week. Bring a real production project and help shape the shared workspace around it.