Boot recreates a project's development context on any machine or cloud agent. A reviewed boot.yaml describes the project's repositories, commands, tools, services, environment requirements, constraints, and profiles. boot up prepares the selected profile, and boot inspect gives agents a structured view of the workspace.

Does boot replace Git, install tools, or start services?

No. Boot prepares repositories and checks declared requirements. It does not replace Git, install tools, or start services.

How do I make a project Boot-ready?

Run boot init from the folder containing the project. Review the generated boot.yaml, add any roles, constraints, or profiles that could not be detected, and commit it with the code. Then run boot up with the profile needed for local work, an agent, CI, or review.

Does boot expose secret values to agents?

No. boot inspect reports environment variable names and availability, but never includes values or decrypted secret material. boot.yaml should contain names and references, never secret values.

Which platforms does boot support?

Boot supports macOS, Linux, and Windows as a standalone binary. Git is required.

Your workspace, wherever you work.

Boot puts your entire code folder on any laptop or cloud agent in seconds. Every repo appears instantly and turns into a real clone the moment you open it.

View on GitHub Setup →

$ curl -fsSL https://useboot.co/install.sh | bash

Quick Start

Run boot from the folder that contains your project. It creates a workspace definition you can review and commit with your code.

# scan the project and create boot.yaml

$ cd ~/code

$ boot init

# review boot.yaml, then commit it with your code

How it works

┌──────────────┐   boot init   ┌──────────────┐
│   MacBook    │──────────────▶│  boot.yaml   │
│   ~/code     │               │  committed   │
│   47 repos   │               │  with code   │
└──────────────┘               └──────┬───────┘
                                      │ boot up
                     ┌────────────────┼────────────────┐
                     ▼                ▼                ▼
              ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
              │    Local     │ │ Cloud agent  │ │ CI / review  │
              │   profile    │ │ agent profile│ │   profiles   │
              │ full context │ │ scoped work  │ │ verification │
              └──────────────┘ └──────┬───────┘ └──────────────┘
                                      │
                                      │ boot inspect --json
                                      ▼
                               ┌──────────────┐
                               │ clear agent  │
                               │   context    │
                               │  no secrets  │
                               └──────────────┘

1.boot init scans the project and creates boot.yaml with the details it can verify

2.You review the file, add project roles or constraints that cannot be detected, and commit it with your code

3.boot up prepares the selected profile's repositories and checks its tools, services, and environment variables

4.boot inspect --json gives agents and automation a stable, secret-free view of the active workspace

One repo or many

Describe every repository in your project, including its path, role, branch, and clone URL.

A setup agents can read

boot inspect --json gives agents a clear summary of the workspace without exposing secret values.

Profiles for every job

Use one workspace definition for local development, coding agents, CI, and review. Each profile selects only what that job needs.

Requirements checked

Boot checks the tools, services, and environment variables your project needs and reports anything missing.

Your commands, written down

Record setup, development, test, and other project commands so people and agents use the right workflow.

Safe by default

Preview changes with --dry-run. Setup commands only run when you explicitly pass --run-setup.

One workspace, different profiles

A profile selects the repositories, commands, tools, services, and environment requirements needed for a specific job. Every profile uses the same boot.yaml.

# prepare the full developer workspace

$ boot up . --profile local

# useful for day-to-day work across the whole project

Handy commands

These are the main commands for creating, preparing, inspecting, and sharing a workspace.

boot init [path]Scan a project and create boot.yaml plus .bootignore.

boot up [path] --profile <name>Prepare the repositories selected by a profile and check its requirements.

boot up [path] --profile <name> --dry-runPreview the plan without changing anything.

boot inspect [path] --jsonReturn a structured, secret-free summary for agents and automation.

boot link <remote> [path]Connect a private workspace map for sharing across machines.

boot save [path]Validate boot.yaml and publish it through the linked workspace map.

See the CLI reference for every command and option.

Frequently asked questions

What Boot records, prepares, checks, and shares.

Make your project Boot-ready

Create boot.yaml, review it, and commit it with your code.

View on GitHub Setup →