Plans, tasks, docs, roadmaps and releases
The workspace your team and its agents share.
DEPOT keeps a team's plans, tasks, docs and roadmaps in one place. Product people work in it directly. Engineers' coding agents keep it current from the tools they already use. Everyone sees the same status, and nobody has to update it by hand.
Who uses it, and how
The people who decide what to build and the agents that build it work from the same plans, tasks and roadmaps.
Everyone sees where things stand
Product managers, founders and stakeholders add plans and tasks and read progress in DEPOT itself, where the work is tracked.
Engineers stay in their own tools
Claude Code, Codex and Cursor know about DEPOT. They check a task out, move it through the lanes and record what they did. Status stays accurate without anyone updating it, and engineers rarely need to open DEPOT at all.
Agents work in parallel
Many tasks across many projects at once. A release coordinator agent can drive a whole release. Every run is tied to its task, and you can reply to it.
Roadmaps for one project, or all of them
Plan a single project or lay every project on one timeline with milestones and a today marker. Plans, tasks, docs, roadmaps and releases live together.
Synced to every collaborator
Each person has a full copy on their own machine, kept in sync with everyone else on the team. It works offline and it is fast. Your data stays on your computer, as files you own.
A desktop app that updates itself
DEPOT runs on macOS, Windows and Linux. It checks for new versions, downloads them in the background and switches on the next restart.
What a team using DEPOT says
InspaceInspace uses DEPOT for our entire product function. Engineers work where they work: their local harnesses know about DEPOT, so they rarely need to open it. Product managers can rest easy knowing they have visibility, engineers don't have to update task statuses, and roadmapping works at the project level and across everything.
Get DEPOT
A desktop app for macOS, Windows and Linux. It updates itself.
All downloads
Opening DEPOT the first time
- macOS
- Open the .dmg and drag DEPOT to Applications. The app is not notarized yet, so the first time, right-click DEPOT in Applications and choose Open. If macOS still says it cannot check it, open System Settings, then Privacy & Security, and choose Open Anyway.
- Windows
- Run the setup file. If SmartScreen says it protected your PC, choose More info, then Run anyway.
- Linux
- For the AppImage, allow it to run as a program (
chmod +xthe file), then open it. For the .deb, runsudo apt install ./<file>.
What is new in 1.2.3-beta
Fixed
- T3 runs use a t3 CLI that matches T3 Code. A T3 run could still fail at once with "T3 Code answered 401 (invalid_credential) for /api/orchestration/shell" when the
t3on PATH was an older version than the T3 Code server, such as an oldnpm i -g t3next to the T3 Code 0.1.3 desktop app: the older CLI issued a session token the newer server does not read. DEPOT now uses the T3 app's own CLI (~/.t3/bin/t3, orbin/t3in whichever T3 home is running) when the app has written one. Otherwise it uses thet3on PATH only when its version is the server's, and refuses an older or newer one before starting anything, with a message naming both versions and how to update (npm i -g t3@nightlyfor a nightly T3 Code, or open the T3 app so it writes its CLI). The harness list shows the same reason instead of offering T3. When DEPOT cannot tell either version it still runs, and a refused token then says the CLI may not match the server and names it. - A T3 launch asks for a model before it starts. Leaving the model on Harness default for a T3 run opened the run and then failed with "Pass modelSelection: the project has no default model", because T3 Code starts a thread only with a model unless its project has a default. For T3 the launch form now reads Choose a model and keeps Start disabled until you pick one, and a run that still arrives without a model stops before starting a thread and says what to do.
- The desktop app notices a new version without a relaunch. It used to check once a few seconds after launch and then every six hours of awake time, so an app left running in the Dock could go days without offering an update unless you pressed Check now. It now also checks when the dashboard loads or reloads, when its window regains focus or is reopened, and when the computer wakes from sleep, at most once every five minutes. The six-hour check goes by the wall clock, so one that fell due while the computer slept runs within a minute of waking. The update prompt also opens once more when a download finishes, even if you closed it while the download was running. A DEPOT that updates from its Git clone checks as before.