One repository at a time
One project per chat: the agent works only in the repository it starts in.
When to work this wayChoose a working setup, then follow the next useful path.
Project Desk works with the workspace your AI client already has. Choose the path that matches how you want to work today.
One project per chat: the agent works only in the repository it starts in.
When to work this waySeveral projects in one run: the agent works across the repositories in one folder.
When to work this wayYour AI client controls which local folders the agent can access. Project Desk never searches the rest of your computer.
Project Desk is your work desk for building software with AI. Your chat and connected agents move the work; the desk keeps a truthful picture of it. Here is the shortest path to a useful first action.
Start your agent inside one repository. It still sees your whole desk, but it can read and change files only in that checkout, so it can finish only that project's work. Queue Agent Queue tickets across several projects and the others will wait.
Start your agent in a folder that holds the repositories you want it to use. One chat can then work through Agent Queue tickets across those projects in a single run. The trade is reach: it can open any repository in that folder, so keep only the ones you mean there, name the project when you hand off work, and check the receipt.
Four ideas cover almost everything. A project holds issues (the units of work). Your desk is the current picture of that work, and queues show what is moving, waiting, or needs you. At any moment a piece of work has an owner — who has the ball.
Shape: the project story and current direction.
Issue: one piece of work with a lasting record.
Attention ask: a concrete action waiting for a person.
Walk: a person trying the running product against named steps.
Return: assigned team work handed back to its requester.
The facts that matter when you work solo with connected agents:
Project Desk works through the AI client you already use: Claude, Claude Code, ChatGPT, Codex, or any MCP client. Connect your AI has the steps for each. You connect once, and the connection belongs to your account, so it reaches every desk you can use; your agent names the desk it means for each piece of work. To check it works, ask your agent to scan your desk once: a short read of your projects and queues comes back.
Short, repeatable ways to do the common things well.
Name the outcome you want, the context your connected agent needs to start, any constraints that bind the work, and what proof will show it is done. A vague title like "fix the thing" is the common miss: it forces the next step to guess.
The Agent Queue is for scoped, well-specified work an agent can finish without a human watching. Give it a clear outcome, firm boundaries, and a definition of done. Dropping ambiguous or judgment-heavy work there is the mistake: it needs a person, not a queue.
When you need a person's judgment or a decision, raise it on the Attention Desk with enough context to act on right away: what you need, why, and what you have already tried. A bare "please look" with no context is the mistake.
Close work by naming what actually shipped and any human gate that still stands between it and done. Closing with no evidence, or leaving a remaining human step unnamed, is the mistake: the next person cannot tell finished from abandoned.
A refusal receipt names the specific next step, for example grant access first, or reassign before revoking, not just that something failed. Read it and take that step. Retrying the same action blindly is the mistake.
What Project Desk is — and, just as importantly, what it is not — when you point an agent at it.
You may notice a versioned PROJECT_DESK.md appear in a connected repository. Your agent writes and updates it; you do not hand-edit it. If AGENTS.md or CLAUDE.md is shared, symlinked, or governed elsewhere, your agent leaves it alone and keeps the Project Desk block in PROJECT_DESK.md.
For the agent's own technical protocol, see For agents.
Start from what you observed. Diagnose before you change anything.
Only the desk text your agent sends it. It cannot open your repositories, terminal, credentials, or local files. Trust & data handling lists exactly what is stored.
Connecting is not the same as making a first call. Ask your agent to scan your desk once, and the use will register. If it still does not, Connect your AI walks through checking the connection.
Reconnect the same connector rather than creating a renamed duplicate, and check that you are signed in as the right account. Connect your AI walks through it.
Sign out and back in, then confirm which email you are signed in with. One person maps to one account by verified email, so the correct email restores the correct desk.
Move it to the right queue. Queues read flow before horizon, so Active and Attention work is never pushed behind Parked; the piece you moved settles into flow order automatically.
An Attention asks a human to look at something. An assigned-work Return hands work you were assigned, but cannot safely finish, back into the shared Return Queue with a clear reason.
They work oppositely. The Agent Queue is a status: an issue is agent-ready exactly while its status is todo, so moving status to or from todo moves it in or out of the Agent Queue (a walk or proof, or a todo issue carrying an open Attention, appears in the Attention Queue instead). The Attention Queue is not a status: an issue is there because it has an open Attention, whatever its status, so moving it to Backlog keeps the ask open. Parking resolves its linked Attention asks and keeps their decision context on the ticket. Resolve an ask without parking to remove it from Attention while keeping its status. Closing the issue also resolves its Attention asks.
Check the queue for an existing ask before you create a new one. If one is already there, reuse or update it rather than opening a second.
The refusal is protecting the work, not blocking you. Reassign or open-handoff the live work first, and the revoke will then succeed.
Read the receipt: it names the real destination, recipient, and resulting item. The change most likely landed where the receipt says, so do not retry blindly. If the destination still looks wrong, contact Support.
Export from Settings → Data & privacy → Export your desk. To reach a person, contact Support; we aim to reply within 5 business days.
An empty desk surface is usually healthy, not broken. Here is what each one means and the next legitimate step.
Nothing needs your attention right now, which is a good sign rather than a problem. When you are ready for more, pick up Active work or open a project from your Project Desk.
No work is queued for an agent yet. The Agent Queue holds tasks an agent can safely finish on its own, without someone watching over it. When you have one ready, add a scoped, clearly specified task here.
No assigned work has been returned. A connected agent sends a Return here when it cannot safely finish something it was given, so an empty queue means nothing is waiting on you.
Nothing has shipped yet. When you close work as done it comes to rest here, so this is where you will find what you have completed.
Still stuck? Contact support. We aim to reply within 5 business days.