Each project can have an agent of its own: one Claude Code process, started in the project's folder when something asks it a question. It answers about the project from its memory and its code. It never edits a file, opens a terminal or makes a checkout.
Asking it
- Ask the project, in the project's sidebar under Board and Devflow, is a chat with its agent. Each answer lists the files it rests on, and a click opens one in a tab.
- An orchestrator linked to the project asks it questions, and has it write the brief a card's session starts with.
- A session working in the project can consult it while it works, up to ten questions a session, and propose what it should remember. A session an orchestrator starts there is told to ask before exploring broadly or picking a pattern the memory may already settle.
It runs under the account of an orchestrator linked to the project. It wakes on the first question, answers one at a time, and stops after ten minutes with nothing asked; the next question picks the same conversation up again.
What it remembers
Its memory is three files in the project, under .devpit/project-agent/:
| File | What it holds |
|---|---|
facts.md |
how the project is: its commands, its layout, its conventions |
lessons.md |
what closed cards taught |
decisions.md |
choices made, each naming the cards it came from |
Each entry is one line with a date and a source: the files it rests on, the cards (#12) or the pull requests (PR #3) it came from. A line without a date or a source is left out. The first question writes the files from the project's own guides and decision records; after that, devpit never writes over them, and every change goes through you.
Proposals you approve
Nothing joins the memory without your click. A proposal waits under the top bar, and on its card, with Approve, Edit and Discard. They come from:
- A closed card. When a card lands in done, the agent reads its comments, its handoff, its review and your corrections, and proposes up to three lessons, and any decisions, with the card as their source.
- A session, proposing a fact, a lesson or a decision while it works.
- Save as fact, under an answer in Ask the project that names files: edit it into one line, and it is proposed resting on those files.
- An entry gone stale (below).
Approved, an entry is written with its source and the day. Discarded, it leaves no trace.
The newest twenty approved lessons go into the brief of a card's session, and into every Devflow review of the project, as items its checklist holds the change to. A card shows the decisions that name it.
Keeping it true
When the agent wakes, the entries resting on files that changed on the default branch since its last check are flagged, and it is asked whether each still holds. What it would change or remove comes to you as a proposal naming the entry it replaces: approved, it takes that entry's place; discarded, the memory stays as it was. Nothing is checked on a timer.
Read-only
The agent runs in the CLI's plan mode, and is refused every write whatever its account allows: file edits, rm, mv, redirects, commits and pushes. Every change to its memory is written by devpit, on your approval.
Turning it off
Settings → Maintenance → Labs → Project agent, on by default. Off, every way to it answers that it is off, Ask the project leaves the sidebar, and closed cards propose nothing. A project whose agent was never asked has no .devpit/project-agent/ folder, and works as it did before.