DevBenchStart in a chat.
Describe the problem. Try a few approaches. Decide what a good result looks like before the work starts.
A place for the work to keep going
The plan is in a chat.
Give it a bench.
You work out what you want with Claude or Codex. Then you copy it into a terminal, keep track of the work, and bring the answer back.
DevBench keeps the brief, gives each session its own place to work, and leaves you a Result to read.
Windows, macOS, or Linux. Your machine. Your projects.
▄▄▄▄
████
▀▀▀▀ Right Click Dev Bench · launcher v0.8.0
████████████████ bench a1 · ~/dev · 2 active projects
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ help for replies · docs for how it works
▀▀▀▀▀▀▀▀▀▀▀▀▀▀
███ ███
▀▀▀ ▀▀▀
Team handbook
Handbook
codex
1. 1018_JH_handbook-links
Fix the handbook links [running on a1]
claude
2. 1018_KO_onboarding
Add the new starter checklist [queued]
Company site
Website
codex
3. 1018_JH_site-copy
Update the contact page [finished on macbook]
Work it out together.
Let the session carry it through.
Make the plan portable.
The chat writes a brief in your shared planning folder, with one launcher line that tells the coding tool where to read it.
Give it room to work.
Type launch. Each session gets a separate branch and working folder. Work that depends on another session waits.
Come back to a Result.
In the morning, read what changed, what failed, and what comes next. Routine work merges for review; you can veto it by reverting.
One line starts a plan
you can read.
A launcher points to the brief. The brief says what to change, what to leave alone, and how the session knows it is done.
It stays in the project folder, outside the chat. A colleague or another computer can pick it up without your conversation history.
This example asks for a small change to a team handbook. The session appends its Result to the same file.
# 1018_JH_handbook-links
## Launcher
Read `Team/Code-Sessions/1018_JH_handbook-links.md`
and do what it says, following
`_Method/CODE-SESSION-PROMPTING.md`.
## Brief
Summary: Fix the handbook's broken links
Repo: Handbook Owns: docs/ Hands-off: everything else
Risk: routine
Attended: no
After: none
Done when: links pass the check and the PR is merged.
Find and fix broken links in docs/. Keep the wording.
Run the link check. List any page you could not reach.Your project is shared.
Your bench is yours.
Activate the projects you work on. Their briefs appear in your menu, with what is running, finished, or waiting, and whose machine is doing the work.
Separate working folders keep concurrent sessions from changing the same checkout. The menu notices a stalled session or a missing heartbeat, so you can see where to look.
You can plan without running a bench. Planners write briefs and read Results in the shared folder.
Two folders.
The tools you already use.
The planning folder holds your shared briefs and project instructions. At Right Click, it is on Egnyte.
The coding folder holds the repositories and each session's working copy on your machine. Claude Code and Codex work there.
Setup suggests sensible defaults and lists what it changed. Opening the launcher does not delete anything. Finished rows stay until you clear them with tidy.
Download it.
Then make it your bench.
Windows
A normal Windows installer, signed by Right Click Inc. It registers DevBench in Installed apps with a working uninstaller and adds it to the Start menu.
macOS
A signed and notarized installer package. Windows on Arm and Linux are on the same page, under Other downloads.
Run it, and it offers the guided setup: your coding folder, your planning folder, GitHub, and the tools your projects need. Then open a new terminal and type devbench. Bring the code it prints to the portal to enroll the machine.
No GitHub account is needed to download. Checksums and signatures are on the download page.
Legacy (PowerShell)
The older scripted installer, for benches not yet on DevBench.
irm https://devbench.rclick.io/install.ps1 | iex # Windows, in PowerShell
curl -fsSL https://devbench.rclick.io/install.sh | sh # macOS and LinuxBuilt at Right Click.
Used on our own work, every day.
We use DevBench to build and maintain our products. It keeps the planning, the overnight work, and the morning handoff in places the whole team can read.
Joining your team?
Open the invite from your colleague and sign in with your work account. The portal takes you through joining the organization.
Join an organization from an inviteSetting up a team?
Name your organization, connect its GitHub repositories, and invite your colleagues. The portal guides each step.
Set up an organization