One config for Cursor

One tool for AI-assisted development. Keep your agents in sync, your sessions tracked, and your context intact across projects, machines, and teammates.

View on GitHub

$ npx openboot agentinit

# Auto-detect stack, generate all agent files

Quick Start

Auto-detect your stack and sync agent context with one command.

# Auto-detect stack, generate all agent files

boot agent init

# ▶ Stack: Next.js, Prisma, TypeScript, Tailwind CSS, Vitest

# ▶ Skills: cloudflare-deploy, github, coding-agent

# ✓ Wrote .cursorrules

# ✓ Wrote AGENTS.md

# ✓ Wrote CLAUDE.md

# ✓ Wrote .github/copilot-instructions.md

How it works

┌─────────────────┐                        ┌─────────────────┐
│  Your Project   │                        │   Generated     │
│                 │   boot agent init      │                 │
│  package.json   │───────────────────────▶│  .cursorrules   │
│  boot.yaml      │   auto-detect stack    │  AGENTS.md      │
│  ~/.boot/agent/ │   merge conventions    │  CLAUDE.md      │
│  skills/        │   detect skills        │  SOUL.md        │
│                 │                        │  copilot-inst…  │
└─────────────────┘                        └─────────────────┘

Detects 30+ technologiesMerges personal and team conventionsPreserves existing filesCI-friendly sync checks

Features

One source of truth

Sync .cursorrules, AGENTS.md, CLAUDE.md, SOUL.md, and copilot-instructions.md from one config. Generates missing files, keeps existing ones in sync

Soul & Skills

Define AI identity (values, boundaries, voice). Boot finds and syncs existing skills following the Agent Skills standard

Conventions that follow you

Personal conventions in ~/.boot/agent/ apply to every project automatically

Team profiles

Share a company-wide baseline via git,conventions, env rules, setup commands

Full dev orchestration

Docker, app processes, env validation, reverse proxy, all from boot.yaml

Editor & CI sync

Define tasks and CI workflows once, generate for VS Code, Zed, GitHub Actions, and Forgejo

Git references

Point agent context at any git repo. Boot clones to a global cache, keeps it updated, and feeds it to your AI tools automatically

Session tracking

Git tracks code; OpenBoot tracks the AI work behind it. Sessions, tasks, and snapshots in .openboot/—plain JSON, no cloud, resume across machines

Optional config

No config needed to get started. Add a boot.yaml when you want control.

# boot.yaml

agent:

description: "E-commerce platform with Next.js and Express"

conventions:

- Use server components by default

- All DB access through Prisma

soul:

identity: "Senior fullstack engineer"

values:

- Correctness over speed

skills:

paths:

- skills/

- shared/workflows/

references:

- [email protected]:Effect-TS/effect.git

targets:

- .cursorrules

- AGENTS.md

- CLAUDE.md

- .github/copilot-instructions.md

apps:

- name: api

path: apps/api

command: pnpm dev

- name: web

path: apps/web

command: pnpm dev

Frequently asked questions

Everything you need to know about OpenBoot.

Agents in sync. Sessions tracked. Context intact.

One tool for AI-assisted development—across projects, machines, and teammates.

Get started