BBAMF Code
North star · 2026-10-05

BAMF Code: desktop vibe coding

A local Lovable meets Codex inside the BAMF desktop app. Prompt to live preview to visual edit to deploy, run against real repos with a worktree per task, diff review and PRs.

Desktop 2.0.34 live Claude Code · Codex · Pi Published with BAMF Code

Build, ship, grow

Every app a creator builds is born inside their brand, their brain and their audience. That is the part Lovable and Codex cannot copy.

01

Brand-native

Apps inherit the brand kit and the shared design catalogue, so the first draft already looks professional.

02

Brain-native

The agent reads offers, voice, ICP and proof, so copy and pricing are real.

03

Ship equals distribute

Deploying to BAMF Sites drafts the launch post, wires lead capture and turns on analytics.

04

One mission control

Claude Code, Codex, Pi and BAMF Bots share one task list and one needs-you queue.

05

Less complexity

No second app or shell. Code reuses sessions, cards, BAMF Browser and Sites.

What it stands on

Most of the hard parts already existed. The missing piece was a native layer for files, processes and git.

BAMF BrowserThe live preview, and the agent's self-QA.
Sites + Domain ConnectWeb preview fallback and one-click deploy.
Projects + templatesA Code project is a project bound to a repo.
GitHub AppPublish to GitHub without a personal token.
Generative UI cardsDiff, run, preview and triage cards in chat.
Jev routerRoutes build and fix intents to the coding harness.

Harness choice

We wrap the coding agents people already have, behind one adapter and one BAMF event model. Safety stays in deterministic code: a worktree per task, approvals for escalations, commands confined to trusted folders.

1 · default

Claude Code

Stream-json CLI. Best approval controls, runs on the user's own plan.

2

Codex

app-server JSON-RPC. Cleanest embedding protocol, covers ChatGPT plans.

3 · bundled

Pi

MIT, any provider or own key, for people with no plan.

Layout and journeys

One Code destination in the existing shell. A task is one worktree, one branch and one agent thread; several run in parallel.

New app from a promptFirst preview in under 60s, clean first commit, hot reload while the agent edits.
Open an existing repobamfaiapp itself opens and runs in Preview with no config.
Live previewThe agent clicks and screenshots its own preview; errors show a Fix chip.
Visual editClick an element, edit its text, land in the right file and line.
Review the diffPer-hunk revert; a hunk comment becomes the next turn.
Ship and deployOne click from a clean worktree to a live bamf.so URL.
Publish to GitHubRepo created, pushed, PR opened from a task.

Roadmap

Each slice in its own worktree, gated on build and tests, checked light and dark, then merged.

S0Plan and session inventory
S1Code layout on recorded agent output
S2Native commands: folders, worktrees, dev servers, files, git
S3Claude Code adapter
S5New app from a prompt with brand-aware starters
S7Ship: commit, push, PR, GitHub, Sites deploy (multi-file)
S8Codex adapter
S4Agent self-QA in BAMF Browser and Fix chip
S6Visual edits
S9Web version on BAMF Cloud worktrees
WINWindows release

Session manager

One BAMF Bot triages every Claude and Codex session and only archives a session once its prompts, context, PR and worktree are accounted for.

665
real sessions
5,148
automated runs filtered
11
active
22
safe to archive

Shipped

Desktop end-to-end test passed 7/7 with a real agent turn: register, worktree, edit, preview, commit.

Sessions sync + strict done rule#1504
/code destination#1505
DSI catalogue at /design#1507
Native Code window#1510
Brand-native starters#1512
Ship tab#1513
Session Manager bot#1514
Codex adapter#1515
Launch polish and accessibility#1518
Multi-file Sites deploy#1520
Desktop E2E driver#1527
Desktop 2.0.34 release#1536