The week this desk is for
Paste it now, read it later
A gnarly stack trace at 6pm. Capture it as code - language preserved - and go home. It is in Inbox tomorrow with a title already on it.
Save it without leaving the file
In onboarding.tsx, select the line about people quitting during workspace creation and save it as a decision. Or ask the agent to search the desk and keep the why. The card shows the file and the branch.
Why this library?
Write the call as a decision: chose the smaller queue library because the team can actually read its source. Future-you asks Memory and gets the answer with a link.
The bug that keeps coming back
You keep capturing the same flaky-test symptom. Connect the Dots notices the pattern: it was never four bugs. It was one.
ADRs minus the ceremony
If you already keep ADRs in git, keep doing that. The desk holds the messy middle - the thread you will not file as markdown.
Guides worth reading first
- Engineering decisions without the ceremonyHonest about not being ADR software.
- Decision logWhat to write, and what to skip.
Quick answers
- Is this architecture-decision-record software?
- No. No git integration, no supersede workflow, no drift detection. Memory is where the why lives for a small team.
- Can I paste a stack trace?
- Yes. Capture as code. Language is preserved.
- Can I save from VS Code or Cursor?
- Yes. A desk key in Settings lets the editor save a selection, and lets an agent search and save when you ask. A decision is filed on the desk with the file and the branch. Your original text stays as you wrote it.
New to the product? Start with How it works or see pricing.