Coming soon

Babbily Dev. Hand off real engineering work. Dev reads your repositories, plans the change, writes and tests it in a cloud sandbox and opens the pull request, with parallel sessions, code review and routines built in.

In development. Details may change before launch.

northwind/storefrontdev/fix-double-charge

Fix the double charge in checkout

Done

Pull request #482Checks passed: 6 of 6Sandbox: pnpm test exited 0

Customers get charged twice when they double-click Pay. Find the cause and fix it.

I can reproduce it. The button fires two POST /charges requests before the first response lands, and each call builds a new idempotency key.

Fixed. The key now comes from the cart, so a second click reuses the first charge, and the button stays disabled while a charge is in flight. I pushed to dev/fix-double-charge and opened a pull request.

PlanAuto

How it works

Three steps from a repository to a reviewed pull request.

01
Connect GitHub
Install the Babbily GitHub App and choose your repositories. One session can work across several, and public repositories run read-only.
02
Describe the task
Tell it what to build or fix. It reads the code, makes a plan, then edits and runs it in a cloud sandbox.
03
Review the pull request
It pushes to a work branch and opens a pull request for you to review, or merges it when you’re ready.

Built for real repositories

Babbily Dev works in its own sandbox, follows your repository’s rules and checks with you at the steps that matter.

Prompt

Review pull request #479 at Standard depth and post what you find.

Connected

GitHub

Search filters #479Standard review

src/search/filters.ts

 export function byPrice(a: Item, b: Item) {
-  return a.price > b.price ? 1 : -1
+  return Number(a.price) - Number(b.price)
 }

Babbily Dev Fix

Price filters compare strings, so "100" sorts before "20". Parse them to numbers first.

Fix itResolve

1 fix, 2 notes · CI auto-fix is on

Code review on every pull request

Review at Quick, Standard or Deep depth, or turn on automatic review for each repository’s pull requests. CI auto-fix takes on failing checks.

Also built in: subagents and parallel sessions with their own pull requests, goals that keep working until they’re met, checkpoints and rewind, and team sharing.

What you can hand to Dev

From a one-line fix to a project split across threads, each one starts with a message.

Fix a bug

Describe what’s wrong. Dev reproduces it with a test, fixes the code, runs the suite in its sandbox and opens a pull request.

Run work in parallel

Start several sessions and follow them on one board, grouped by where each one stands. The ones waiting on you come first.

Review a pull request

Ask for a review at Quick, Standard or Deep. Findings come back by file and line, and nothing goes to GitHub until you post it.

Comment on the diff

Select lines in the changes and say what should change, as you would in a review. Your comments go to Dev with your next message.

Put it on a routine

Start a session on a schedule, when something happens on GitHub, or from your own tools through its API. Each run works as you.

Set a goal

Give Dev a goal with /goal and it keeps taking turns, checking after each one, until the goal is met or it reaches its turn limit.

Split big work into threads

A project’s coordinator plans the work and starts a thread for each task, each with its own branch and pull request.

Steer it while it works

Send a message while a turn is running and Dev takes it into account without starting over. Send now if it can’t wait.

It asks first

In Ask mode Dev checks before it edits a file or runs a command. Approve once, or always allow commands that start the same way.

Every leading coding model, your pick

Choose from 13 leading coding models for each session and set how much it reasons. Each model has its strengths, so pick the one that suits the work, and the session keeps it.

Everything in Babbily Dev

A closer look at what’s built in, from the first message to the merged pull request.

Sessions side by side

Run several sessions at once, up to your plan’s limit, each in its own sandbox.

A status board

Sessions group by where they stand: Waiting on you, Ready for review, Landing, Working, Idle and Resolved.

Steer while it works

Message a running turn and Dev takes it into account without starting over, or use Send now.

Side chat

Ask /btw why it picked an approach or what’s left, and get an answer beside the session. Only you see it.

Rewind

Rewind the conversation to an earlier message, or restore the code to an earlier turn. Undo a rewind until you send again.

Goals

Set a goal with /goal and Dev keeps taking turns, checking after each one, until it’s met.

Tasks and questions

Dev keeps a task list as it works, and asks you a question when the choice is yours.

Suggestions

Ghost text suggests your next prompt, and suggested sessions start with a click.

Compaction

/compact summarizes a long session, with an optional focus, so the next turn has room to work.

Shared sessions

Share a session with teammates, and find the ones shared with you under Shared with me.

Usage details

A ring in the composer shows your allowance. Details break it down by model, sandbox time and network.

Three modes, your call

Choose how much Babbily Dev does before it checks with you.

Plan

Reads and plans; changes nothing.

Ask

Asks before it edits files or runs commands.

Auto-accept

Edits in the sandbox and pushes to its work branch without asking. Commands, websites and any other push or pull request still ask.

Included in every Babbily plan

Babbily Dev comes with every plan, Free included. Model use, sandbox time and network come out of your plan’s shared allowance at provider cost, with no markup.

Plan

Sessions at once

Free

Personal

Premium

Ultra

Team

Frequently asked questions

Babbily Dev is on its way

Dev is in development, and details may change before launch. Everything else in Babbily is ready today, on the same account Dev will use.

Try Babbily