Work with a coding agent for a week and loose ends pile up. You spot a bug while the agent is busy with something else. It finishes a task and mentions two things it left alone. A good idea comes up at the end of a long conversation, and by morning that conversation is buried under ten newer ones. Projects is a small issue tracker on the exe desktop that catches all of it, and Claude Code can read it and write to it as easily as you can.
A list where everything has an address
Projects looks like the rest of exe: one window, with your projects on the left, a project's issues in the middle and the chosen issue on the right. An issue is one thing to do, such as a bug, a feature or a question. It has a title, a description, pictures if you have them, and a conversation underneath.
Every issue gets an address: the project's short name and a number, such as EXE-12 or PROJ-15. An address never changes and is never given to another issue. That sounds like a small thing, but it is what lets you and an agent talk about the same piece of work without copying it back and forth. Once Claude knows where the tracker is, "fix EXE-12" is a complete instruction.
Hand it over
When an issue is ready, right-click it and choose Send to Claude Code.
The Claude Code window comes forward with a new conversation, already in the project's folder. Its first message is the whole issue: the description, every comment so far, and a short note that asks Claude to read the project's instructions, do the work, check it and report back. Attached files are named, not sent along. You do not type a word.
Send to Codex does the same for Codex. To start from a blank page instead, right-click the project itself and choose Open in Claude Code: you get a new conversation in the project's folder, waiting for you.
Nothing about Claude Code changes. If it has never worked in that folder, it asks whether you trust it, and it asks for the permissions you have not already given it.
See who is on it
While Claude works in exe's Claude Code window, the issue says so. A line appears under the title with a pulsing green dot, the agent's name and how long it has been working since your last message.
The line does not care how the agent got the issue. Send to Claude Code is one way. Typing "have a look at PROJ-6" into a conversation that is already open in the Claude Code window is another. The line goes away when Claude finishes, or stops to wait for you. Come back to an issue days later and you can see at a glance whether someone is already on it.
Claude writes back
An agent does more than read the tracker. Projects comes with a command an agent runs in its terminal to file an issue, read one, comment on it and close it. Give the agent a signing key and a name of its own, and everything it writes carries that name, not yours.
Tell it once how you want this used, in the project's instructions file: CLAUDE.md for Claude Code, AGENTS.md for Codex. A few lines are enough. Put in the command's full path on your machine, since it stays in the folder where Projects was installed:
Issues for this project are in
Projects. The command is
~/exe-projects/exe-projects,
and `help` lists what it does.
Read an issue with `show EXE-12`.
Found something outside your
task? File it with
`new . "Title" -m "What you saw"`
and carry on.
Before you start an issue,
comment your plan on it as a
checklist. When you finish,
tick the checklist, report what
you did, and close the issue
with the commit.
Send to Claude Code asks for a report, but not where to put it. Lines like these put the plan and the report on the issue, where you will look for them.
Here is a finished one: a request to reorder the projects in the sidebar by dragging them. Claude posted a plan, ticked each step as it was done, and then reported what it built, how it tested it and what it left out, with a screenshot. Then it closed the issue.
Everything you need to judge the work is on one page, and it stays there after the conversation has scrolled away.
The loop
With those lines in place, the work goes round like this:
- You write down what you want as an issue. If it is about something you can see, attach a screenshot.
- You send it to Claude Code, or mention its address in a conversation.
- Claude reads the issue and the project's instructions, posts a plan and starts. The issue shows that it is at work.
- Claude reports on the issue and closes it. Anything it noticed on the way becomes an issue of its own.
- You read the report. If something is off, reopen the issue, say what, and send it again. The new conversation starts with everything, the last report included.
On the machine where exe is made, the loop takes even fewer clicks. A small script watches the tracker. When a comment asks for work, like the "Claude, build this." in the picture above, the script starts Claude Code on that issue by itself. That script is not part of exe. Send to Claude Code is the same step, done by hand.
Try it
Projects is one of exe's extras: a program of its own that you add when you want it. Send to Claude Code needs exe 2026.10.15 or newer, with Claude Code and tmux on the same machine as exe.
- Choose Help → Welcome…, and press Extras… on the Apps card.
- Go to the Projects page. If Projects is not on this machine yet, the page gives you a line to paste into Claude Code, and Claude installs it. If Projects is installed but the page cannot find it, type its folder and press Find.
- Make sure the box is ticked, press Continue until you reach Review, and press Apply. Projects appears on the desktop.
- Make a project. Under Directory, type the full path of its folder on the machine that runs exe. That is where Send to Claude Code opens.
- Write an issue, right-click it and choose Send to Claude Code.
One caution: files you attach to an issue are kept in IPFS, where anyone who learns a file's address can fetch it. Keep secrets out of them.
The manual has the details, and the source is at github.com/livid/exe-projects.