2found
ENVI
All tools
2build / Product engineering

From a task
to tested work.

Turn a feature or bug fix into reviewed, tested code. 2build gives your coding agent a workflow from plan to QA, with a local commit and evidence at the end.

Install with your agentRead the docs
Your project. Your coding agent. Your release decision.
One ticket → verified handoffAutopilot
You describe the change. The workflow carries it through.
  1. 01
    Plan the change

    Review the plan and prototype before the build.

  2. 02
    Build and repair

    Let the agent implement, review and fix the work.

  3. 03
    Verify the result

    Run project checks and QA against real behavior.

  4. 04
    Get the handoff

    A local commit with evidence, or a named blocker.

Workflow illustration. Completion requires the checks to pass.

Works withClaude CodeCodexAntigravityOMPGrok
01 / Keep the work moving

Less directing.
More finished work.

A workflow for the agent you already use.

01

Review the direction early

See the plan and, for UI work, a prototype before implementation. Correct the scope and flow while changes are still cheap.

02

Finish the engineering work

Autopilot carries one ticket through implementation, review, repairs and QA in your current agent session. You choose the model before you start.

03

Pick up where you left off

The plan, checkpoints and check evidence stay on disk. Give Autopilot the ticket ID after a restart to resume with that context.

02 / Start with one prompt

Give your agent
the setup task.

Open your coding agent with terminal access.
Copy this prompt, then follow its setup checks.

Install 2build
Install 2build for the coding agent I am using. Follow
https://raw.githubusercontent.com/2found/2build/main/docs/install.md. Detect my OS and
current agent, reuse a working bbs installation or install the CLI, then install the
skill pack for this agent only. Verify bbs --version and the installed skills; report
any missing prerequisite instead of claiming success. Tell me whether I need to restart
and give me the exact Autopilot invocation for my agent to run my first small task.
01

Get your agent ready.

The CLI and skill pack work together.

Your agent detects your OS, installs or reuses bbs, installs its own skill pack, then verifies both. Claude Code and Codex need their CLI on PATH. Restart the agent when setup asks you to.

macOS or Linux: Homebrew or a release archive. Windows: WSL. Use your existing model account; normal usage charges apply.

Installation and troubleshooting
02

Choose one small task.

Make the result easy to check.

Open a Git repo, choose your model and ask Autopilot to handle one feature or bug. Review the plan and UI prototype, then paste its goal handoff into the same agent. The build ends with a local commit and check evidence, or a specific blocker.

Run your first ticket

No project yet? Start with the Bun/Hono template. No Orca is needed for your first Autopilot ticket.

Full quick start and agent reference Markdown for agents (.md)
03 / Start small, grow the workflow

One task today.
A project when ready.

Use Autopilot for a scoped feature or bug in your current checkout. Create your preferred branch first if you want isolation.

Choose a focused skill for planning, debugging, review or copy. Add Foreman and Orca when dependent tickets need coordinated workers.

Bring usable project checks. A missing browser, runtime or required check is reported as a blocker; it does not count as verified work.

04 / Before your first ticket

A few practical
questions.

A 2found product.

Your next change
starts here.

Get the setup prompt