Platform
Run the factory, not the agents.
Named agents, schedules, the organization's controls, and the apps you run it from.
Part of your own software factory. See the whole line
Everything around the agent, at a glance
- Builder defaulttests, video, previews, merge requests
- Reviewerreads diffs, files findings under security-audit
- Opsdeploys, backups, cloud preflight
Each runs on Claude Code or Codex.
Agents
Named personalities with their own prompt. Hire one or write your own.
Each tile above is a section on this page. Two more have their own page.
Agents
Named personalities with their own prompt, skills and tools.
Mention one in a workspace's chat to put it to work, or give it recurring work on the Schedule.
- Builder defaulttests, video, previews, merge requests
- Reviewerreads diffs, files findings under security-audit
- Opsdeploys, backups, cloud preflight
Each runs on Claude Code or Codex.
Hire from library
A library of ready-made personalities:
- project manager
- team lead
- full-stack engineer
- sales
- growth
- SEO
- GEO
- content
- design
- QA
- security
- DevOps
- data
Hiring copies one into your organization. Your edits stay yours.
Tools are picked per piece of work
Each task gets only the tools you select for it.
A fresh container for each run
Each scheduled run starts in a fresh container.
Recurring work, with a memory of what earlier runs found.
Run once, every day, on selected weekdays, or every N days.
- Nightly backup0 3 * * *ok
- Security audit, weekly0 9 * * 1ok
- Dependency bump0 7 * * 3silent run flagged
Send a task to the agent
A prompt, run in a fresh container.
Send a task to a named agent
The same, run as that agent with only the tools you select.
Post a chat message
A message to a workspace's chat, on schedule.
A watchdog
A run that never reports back is marked failed, and an owner is told.
Continuity: why run 40 differs from run 1
Each run reads what earlier runs found, and adds what it finds.
Consolidate folds a task's history into one digest.
What previous runs of this task already established
- Run 40this execution
- Run 39published under security-audit
- Run 38published under security-audit
- Run 37stopped early
Each run builds on the last.
Scripts kept running, restarted when they exit.
A poller or a sync that should keep running, whether or not anyone has the workspace open.
DevBench restarts a watcher that exits and posts to the chat when it does.
Stop takes it out of service until you start it again.
- alive invoice-syncrestarted 2 times this week
- alive queue-monitorup 6 days
$ devbench watcher add <name> --script-file <path> --interval <n>
Create one from the workspace.
$ devbench watcher list
This workspace's watchers and their status.
$ devbench watcher logs <name> --tail 100
The watcher's own output.
$ devbench watcher runs <name>
Its start-to-exit run history.
$ devbench watcher edit <name> --script-file <path>
Change its code or schedule.
Shared skills with named credential profiles.
Any workspace's agent can run it.
- Base environmentRegion
- staging encrypted, never returned
- live encrypted, never returned
$ devbench tools run aws --env live -- s3 ls
One tool, a profile per environment
A profile per environment, such as staging or prod. A run picks one with --env.
- aws profile: read-only stored encrypted
- stripe profile: test stored encrypted
- devbench videorecords a real browser on the preview
Written once, run by any workspace's agent
Its one-line description tells agents when to use it.
$ devbench tools list
The team's shared tools and skills.
$ devbench tools show <name>
A tool's info, env vars and profiles.
$ devbench tools run <name> --env prod -- <args>
Run one under a named credential profile.
Releases
One version across every repo.
A release ships chosen repos together, under one version.
- 1
Gate
Source merges into the gate, in each repo.
- 2
Cut
A release branch is cut from source.
- 3
Record
Commits go into the changelog.
- 4
Ship
Merged into production.
- 5
Tag
Tagged
v<version>.
- sourcefirst stage
- gatebefore production
- productionlast stage
Show commits lists what shipped. Resume picks up a repo that did not finish.
One record of everything that happened to you.
Mentions, finished work and failed deploys, newest first.
- Alex mentioned you in upload-rate-limit09:50
- Agent finished Onboarding emails, step 2 of 609:12
- Nightly backup run was silent03:00
Markdown renders
Notifications render Markdown. Tap one to open its subject.
Two channels on the phone
Chat and Inbox alerts are kept apart.
Quiet means quiet
Workspaces you have not turned on stay silent.
Owners hear what only owners can fix
Broken cloud accounts, failed integrations and failed backups.
Team
Owner, maintainer or member. Joins by invite code, not sign-up.
Your role and workspace assignments decide what you reach.
- Sam ownerevery workspace
- Alex maintainerevery workspace
- Lee memberupload-rate-limit, Onboarding emails
Members see only the workspaces they are on.
Owner
- Workspaces they reach
- Every workspace in the organization
- Also
- Roles, invite codes, API keys, organization settings
Maintainer
- Workspaces they reach
- Every workspace in the organization
- Also
- Chooses which workspaces show on their own board
Member
- Workspaces they reach
- Only the workspaces they are assigned to, plus any they created
- Also
- Nothing more
Deploying is its own permission
Production deploys and cloud changes need it, and no role includes it, not even owner.
Previews stay open to all.
Invite codes
There is no self-serve sign-up: you give each person a code that sets their role. You cannot change your own.
The defaults every workspace inherits.
Eight settings areas, grouped by what each one decides.
AI
The agent sign-in and the standing instructions for every workspace. Owners set them.
Standing instructionsevery workspace## Organization (managed)
- the stack
- the review etiquette
- the library that must never be used again
SaveApply to all workspacesWorkspace defaults
What every new workspace's container includes.
Board stages
Rename, reorder, add or delete the columns.
Integrations
Your GitHub and GitLab tokens, to import repos and push.
Notifications
Where outside events arrive, and how they reach the team.
Git flow
The stages work moves through, first to production.
Backup
App
Versions of the desktop app and the CLI.
A few hundred kilobytes that hold your configuration.
Code is never included.
- 1
Push
Each workspace's work is pushed to its branch.
- 2
Record
Your configuration is saved as one file.
Secrets are off by default. Turned on, they are included encrypted.
Restoring
A dry run is the default. It shows what a restore would change.
Nothing is ever deleted.
Extra items are reported and left alone.
Merge is the default.
Existing data is kept unless you choose to overwrite.
Code is not in the backup.
Restored workspaces point at the same repo and branch.
User accounts, other people's git tokens and media files are reported, not restored.
$ devbench backup
Run a backup.
$ devbench backup list
Past backups, newest first.
$ devbench backup diff <file>
What restoring this file would change, in both directions.
$ devbench backup restore <file> --apply
Restore it. Without --apply it is a dry run.
What AI costs, per workspace.
Look at 30 days, 90 days or 12 months.
See where the money goes, by model, workspace and day.
Older spend is estimated, not counted. Newer spend is exact.
- upload-rate-limit$62
- Onboarding emails$38
- Media share-link audit$21
- up production, mainYour server, over SSH
- up stagingCloud static hosting
- preview feature/upload-rate-limitstops when idle
Monitor shows the live health of the server.
The API from your own scripts.
A key has your account's access. Treat it like a password.
curl -H "Authorization: Bearer devbench_sk_…" \
https://<your-host>/…Shown once, when created. Revoke switches a key off; Delete removes it.
The same account, everywhere.
One account works in the web app, desktop app, mobile app and CLI.
Web
The full app, with the editor.
One task, one merge request, waiting on a person.
- Agent opened
!18409:48 - Recording attached to #1209:47
- 42 tests passed09:45
The board, each workspace's tabs, Inbox, Team and Settings.
Each workspace opens in a browser VS Code, on its branch.
Desktop
The app in a native window, plus Open on my PC in your local VS Code.
Windows, macOS and Linux.
- Clones to~/DevBench/upload-rate-limit
- On the branchfeature/upload-rate-limit
- Opens withcode <folder>
Uses your own git credentials.
$ code ~/DevBench/upload-rate-limit
The same app as the web. Sign in with your usual account.
Open on my PC clones the repos to your machine, on the workspace's branch, and opens them in VS Code.
- What it needs
- git, and VS Code with the
codecommand on PATH. - Where workspaces go
- Workspaces → Choose workspaces folder… sets where they are cloned.
- Where to get it
- Get DevBench, at the foot of the sidebar, has an installer for each platform.
Mobile
Chat, the Inbox and the board, from your pocket.
iOS and Android.
!184; it needs a person to merge.The agent is asking
Reply with a wait time when over the limit?
| Screen | What it shows |
|---|---|
| Workspaces | The board, as cards or a calendar. |
| Chats | Every workspace chat, with unread badges. |
| Inbox | Assignments and updates. |
| Chat | Live chat. @agent asks the workspace's agent. |
Attach photos and files, or send them into a workspace from the share sheet.
A retry after a dropped connection does not post a message twice.
CLI
devbench on your machine, and in each workspace.
$ devbench list
Your workspaces.
$ devbench setup <id>
Clone a workspace locally on its branch.
$ devbench create -n "Name" -r <repo-id>
Create a workspace.
$ devbench commit
Push all repos, and archive the session's chats and memory.
$ devbench task done 12 --note "Rate limit in place; 42 tests pass" $ devbench video record upload-rate-limit --task 12 $ devbench mr create --target main
- On your own machine
- Creates workspaces, clones them, and pushes your work back. Needs
gitandpython3. - Inside a workspace
- How an agent reports on tasks, chat, docs and deploys.
- Work on this locally
- One command clones every repo on the workspace's branch.
Set up with you
Start with one real project.
We set up your factory with you and ship one project from your roadmap.