DigitalDesk
Name a case or find existing work.
Starting work
External agents
Connect once. Work from any agent.
Use the same Digital MCP endpoint from Codex, Claude, Cursor, or another compatible client. Product Cases keep the research scope, evidence, and human approvals together.
/desk/mcp
Authentication and case-scoped authority stay in Digital Desk.
Native instruments
One credential, explicit faculties.
Issue an agent credential
The token is shown once, stored only as a hash, and can be revoked here. It can read the approved case and call only the selected native providers.
Issued credentials
No credentials issued yet.
Sign in to issue or revoke agent credentials. The MCP endpoint remains discoverable without a token.
Initial framing
Refine the case.
Review the name and add enough context to frame the work. Nothing is handed to an agent yet.
You have another draft here.
Your course idea is ready. Your other draft will stay safe.
Product Case
Loading case…
Restoring the case summary and its next action.
Human Gate A
Approve what the agents may investigate.
This frame becomes immutable authority for one run. Product and Incident changes still require their existing explicit controls.
Filled from your Lab answers. Change anything here, then approve it.
Agent handoff
Start this exact investigation.
Gate A is approved. Starting consumes it once and binds all instrument receipts to the run.
Your helper reads your case text. The clock starts when you press Start, so start only when your helper is ready.
What you do yourself during the run
Helper access is for this case only. It ends on the date shown after you start (five days for most accounts), and you can revoke it. Read-only means your helper can read this case but cannot use any app or leave anything for you.
What your helper will do
The agent can research, propose, and append receipts. Deciding proposals, signing Gate B, and finalizing stay human actions here; Product owns Save and release.
Run evidence
Agent work trace
This view comes from immutable, server-clocked Digital run receipts. Agent-reported notes remain visibly distinct from instrument-observed evidence, and private receipt metadata is not exposed.
Gate-A instruments
No durable agent work receipts yet. Selected executable instruments remain pending until their native provider records successful work.
Proposals
Something the agent prepared. You decide.
Each proposal names an artefact, carries the fingerprint of the exact payload you would sign, and stays pending until you accept or reject it. The agent never applies a proposal.
No proposals yet. The agent leaves proposals here while the run is live; each one waits for your decision.
Human Gate B
You sign it.
Signing binds you to the exact fingerprints of the accepted proposals for this run. It is one-use: finalization consumes it once.
- Sign-off id
- Fingerprint of the signed set
- Signed on
- State
Finalize
Make the thing.
Finalizing uses your Gate B sign-off once and records a release authorization bound to the signed fingerprints. Product owns Save and release; Digital never marks the case released on its own.
- Release authorization
- Fingerprint of the signed set
- Authorized on
- Stage
- Release door
- Product owns Save and release. Carry this authorization into Product; Digital stays at release-ready.