Product tour

See how Babel works, before you run it.

This is an accessible, clearly labeled walkthrough of the interface and workflow. Everything below is illustrative reference content — not a live session, not captured execution output, and not a copied verification receipt.

Chat — the daily default

A multi-turn conversational loop with visible tool activity. Babel reads, edits, and verifies — you approve at each step that needs it.

Reference preview — illustrative walkthrough, not a live run

You
  Fix the failing webhook retry test.

Babel
  ▸ Read src/webhooks/handler.ts
  ▸ Read tests/webhooks/handler.test.ts
  ▸ Edited src/webhooks/handler.ts
  ▸ npm test -- webhook
  ✓ 18 passed

  Completed · 1 file changed · verified

Illustrative transcript written for this tour. It is explanatory content, not a Babel verification receipt.

Plan — a gate before mutation

Plan produces a reviewable plan first. Nothing is applied until you approve it in your session.

Reference preview — illustrative walkthrough, not a live run

You
  babel plan "Split the auth module safely"

Babel
  Plan (2 steps)
  1. Extract session helpers into auth/session.ts
  2. Update call sites; run test suite

  Awaiting your approval — nothing has been changed.

Illustrative transcript written for this tour. It is explanatory content, not a Babel verification receipt.

Deep — more structure, not a reliability upgrade

Deep loads the governed pipeline with adversarial review for riskier work. More ceremony means more cost, not a correctness score.

Reference preview — illustrative walkthrough, not a live run

You
  babel deep "Harden the migration path"

Babel (governed pipeline)
  ▸ Orchestrator planning
  ▸ Executor: 3 edits
  ▸ Adversarial QA review: 2 findings resolved
  ✓ Verification contract finalized

Illustrative transcript written for this tour. It is explanatory content, not a Babel verification receipt.

Evidence — the harness checks completion claims

A model's "I'm done" is not success. Only authoritative project checks can green a completion; otherwise the outcome is labeled unverified.

Reference preview — illustrative walkthrough, not a live run

Outcome labels
  ✓ VERIFIED_COMPLETE   — required checks ran and passed
  ~ UNVERIFIED_PATCH    — changes exist; checks did not run
  ✗ BLOCKED             — isolation or policy stopped the session

  exit 0 only for verified/unverified-patch terminals

Illustrative transcript written for this tour. It is explanatory content, not a Babel verification receipt.

Ready to try it? Start with thequickstart — the no-key checkpoint works without any provider credential.