Skip to content

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

Agents

Named personalities with their own prompt. Hire one or write your own.

Read moreabout Agents

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.

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.

  • 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.

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.

devbenchinside the box
  • $ 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.

One tool, a profile per environment

A profile per environment, such as staging or prod. A run picks one with --env.

Written once, run by any workspace's agent

Its one-line description tells agents when to use it.

devbenchinside the box
  • $ 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. 1

    Gate

    Source merges into the gate, in each repo.

  2. 2

    Cut

    A release branch is cut from source.

  3. 3

    Record

    Commits go into the changelog.

  4. 4

    Ship

    Merged into production.

  5. 5

    Tag

    Tagged v<version>.

  1. sourcefirst stage
  2. gatebefore production
  3. 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.

  • 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.

  • 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.

  • Workspace 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

    Below.

  • App

    Versions of the desktop app and the CLI.

A few hundred kilobytes that hold your configuration.

Code is never included.

  1. 1

    Push

    Each workspace's work is pushed to its branch.

  2. 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.

devbenchon your machine
  • $ 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.

The same account, everywhere.

One account works in the web app, desktop app, mobile app and CLI.

Web

The full app, with the editor.

The board, each workspace's tabs, Inbox, Team and Settings.

Each workspace opens in a browser VS Code, on its branch.

Set up with you

Start with one real project.

We set up your factory with you and ship one project from your roadmap.