Claude's answers, checked by other AIs before you read them.
Desks is a way of working for Claude Code. Your work sorted by topic, recommendations attacked by models from other vendors, heavy reading sent to cheaper workers, and a written close so the next session starts where this one stopped.
Set up Desks in this folder. Get version v0.1.7 of https://github.com/rivera-ernesto/desks, read its INSTALL.md and follow it. First show me the list of files you will create or change, and wait for my yes. Keep everything I already have.
It copies one skill and three workers into the folder and adds one marked block to CLAUDE.md. It asks before touching anything you already have. What the prompt does, step by step.
What a session looks like
desk sell-camera
sell-camera · new · history on · review: cross-vendor. What are we selling, and by when?
My old DSLR kit, this month. What should I ask for it?
Ask 95, accept 80. My first number was 120, taken from what similar kits are listed at. Two of three reviewers pointed out that unsold listings show what does not sell. Sold ones went for 70 to 100.
One reviewer suggested offering shipping. I did not follow that: you asked for a quick sale, and disputes on a shipped old camera cost more than the extra reach.
Review: [converged] · 3 vendors · receipt 5d1c0a77e2
An invented example. See the files this session leaves behind.
Write the way you think
You do not have to prepare a clean brief. A Desk is built for input like this:
ok so the garage thing.. my sister says saturday but i think the 14th is the school fair?? not sure
also the bikes, are they even worth selling or just give them away. and the neighbour said something about a permit
oh and dont post anything yet
garage-sale · new. I heard four things:
1. The date. I checked: the school fair is on the 14th, 9 to 1. The Saturday after is free. Proposal: the 21st.
2. The bikes. Two similar ones sold nearby for 40 to 60 last month. Worth selling, as a pair.
3. The permit. I could not confirm this either way from the town's site. That one needs a phone call, and it is yours to make.
4. Nothing gets posted. Noted. Drafts only until you say so.
Review: [converged] · 3 vendors · receipt 8a41f0c2d7
An invented example. Claude sorts what you said, checks what can be checked, says what it could not verify, and keeps the "don't" as a rule for the whole topic. If you had also mentioned your tax return, it would have filed that under its own topic and carried on.
Short requests, completed in the open
Every assistant adds things to what you type. A Desk shows you what it added, and where each addition came from, before it starts:
Draft the letter about the leak.
Doing: draft the letter about the leak
+ topic notes (README, What we learned): to the landlord · firm, not hostile
+ your profile (Never without asking): no legal threats
+ my assumption: a second letter, since the notes say the first got no answer
+ Desk: a draft only; nothing is sent
no, this one goes to the building manager
An invented example. A guess is labelled as a guess, never as a rule. As the notes on a topic grow, what you have to type shrinks. It shows what Desks and your own files added: the instructions Claude gets from its maker are not ours to show.
What you get
Reviewed answers
Advice and anything high-stakes goes, with names removed, to free models from other vendors. Claude has to answer each objection, and the reply says how it was reviewed.
It leads
It opens with where things stand and the move it would make next, carries the good habits for you, and offers what you did not ask for when it has evidence. One sentence turns that off.
Proposals, not questions
Claude settles what it can and brings a reviewed proposal. It waits for your word on five things: money, anything public, contacting someone, access, and anything permanent.
One topic, one folder
State, decisions and a note per session, in plain files. History, branches and pull requests happen under the hood. You never type git.
Your plan lasts longer
Reading, screen work and long outputs go to workers on a smaller model. The session proposes its own close before it gets expensive.
It picks up where it stopped
At the close, the topic's notes are rewritten so a fresh session can continue from them alone.
It fits around your setup
Your rules win. Desk adds to what you have and can use your folders, your agents, and other AI subscriptions you already pay for as reviewers.
What it needs
- A paid Claude plan and Claude Code (the desktop app's Code tab, or the terminal).
- For cross-vendor review: Python 3 and a free OpenRouter key. Without them, a second Claude reviews instead, and the reply says so.
- Nothing else. Git and GitHub are used when they are there.