Pro Feature

Developer Workbench: Git round-trip, built in

No more tab-switching between your Kanban board and your IDE. Developer Workbench auto-creates branches, syncs PR status in real time, and advances Bolt stages on every push, review, and merge β€” so your board always reflects reality.

The problem

Your board is lying to you

Today, once a developer picks up a Bolt, BoltOps loses visibility. Stage transitions are manual button clicks, the board goes stale, and PMs check GitHub separately to know if a Bolt actually shipped. Developer Workbench fixes this with a Git-native feedback loop.

🚫

10–15 min handoff friction

Developers manually copy intent docs, find the right repo, create a branch, and set up their environment. Every. Single. Bolt.

😢

No progress signal

BoltOps can’t tell if a Bolt is being actively coded, stuck, or abandoned. The board is perpetually stale.

πŸ”„

No code-back loop

When code is pushed, reviewed, or merged, BoltOps doesn’t see it. The PM has to check GitHub separately.

How it works

Git events drive your board

Developer Workbench watches your repository via a lightweight GitHub App. Push, PR, review, and merge events auto-advance Bolts through their stages β€” no manual clicks, no stale boards.

1

Bolt assigned β†’ branch created

When a developer is assigned to a Bolt, BoltOps auto-creates a feature branch (feature/bolt-042-user-auth) and commits the full intent document as .boltops/intent.md.

2

First push β†’ stage: Generate

The first commit pushed to the feature branch moves the Bolt to the Generate stage automatically. No button click needed.

3

PR opened β†’ stage: Verify

Opening a pull request signals the code is ready for review. The Bolt advances to Verify and the PR gets a status comment with acceptance criteria progress.

4

Review β†’ Iterate or Ship

An approved review moves the Bolt to Ship. Changes requested sends it back to Iterate. The board updates in seconds, not hours.

5

Merged β†’ Completed

When the PR merges to main, the Bolt is marked complete. No one has to remember to drag a card.

Features

Everything in the Workbench

A complete Git-to-board bridge with developer-first UX.

πŸ”Œ

Auto-branch creation

Feature branches created instantly when Bolts are assigned. Configurable naming pattern: feature/bolt-{id}-{slug} by default.

πŸ“‹

Copy-to-clipboard context

One click copies the full intent document, acceptance criteria, architecture constraints, and CLAUDE.md excerpt as a ready-to-paste prompt for your AI coding tool.

πŸ”—

IDE deep links

Open the right repo and branch in VS Code, Cursor, or Google Antigravity with a single click. Each developer picks their preferred IDE in settings.

⚑

Webhook-driven stage sync

Push, PR, review, and merge events from GitHub auto-advance Bolt stages. Your board reflects reality in real time, not when someone remembers to update it.

πŸ“ˆ

Git activity feed

See every commit, PR, and review in the project Workbench tab. Per-Bolt activity panels show exactly what happened and when.

πŸ—ƒ

.boltops/ context files

Intent documents and structured metadata committed to the feature branch so they’re available in the IDE, in CI, and as context for AI agents.

IDE support

Works with the editors your team actually uses

Developer Workbench supports the three IDEs AI-first teams are choosing between. Deep links open the right repo and branch with one click.

πŸ”΅

Visual Studio Code

Full support via vscode:// protocol. Clone, branch checkout, and file navigation from any Bolt card.

🟠

Cursor

Deep links via cursor://protocol. Cursor’s AI features pair perfectly with the context prompt builder.

πŸ”·

Google Antigravity

Early support for Google’s VS Code fork. Manager View integration planned for the IDE extension phase.

Availability

Available on Pro, Studio, and Enterprise

Developer Workbench is a configurable toggle on Pro tier and above. Enable it in Settings, connect your GitHub repo, and the Git round-trip starts working immediately. No extension to install, no CLI to configure.

Ready to ship at Bolt speed?

Join engineering teams that have replaced sprint ceremonies with AI-orchestrated workflows.