How it works

Preview first. Apply only after purchase.

Bring Your AI has two user-facing paths: move an existing Claude Code or Codex setup, or build a first setup from public work history.

Free Preview

Preview is intentionally small. It does not show mappings, file paths, generated memories, validation notes, estimated size, or risk.

bringyour preview --from claude-code --to codex
bringyour preview --build --github yourname --to codex

Preview answers only: supported or not, existing setup can be kept, original files will not be changed, and where to buy.

Path 1 — Move My Setup

Use this when Claude Code or Codex already feels like yours and you want that operating context in the other tool.

bringyour migrate --from claude-code --to codex --policy merge
bringyour migrate --from codex --to claude-code --policy merge

Path 2 — Build My First Setup

Use this when you do not have a harness yet. Bring Your AI reads public signals and creates a starter setup for Claude Code or Codex.

bringyour build --github yourname --to codex
bringyour build --github yourname --to claude-code

Build sources include GitHub, RSS/Atom, Hacker News, Dev.to, and Stack Overflow. Optional synthesis can use Anthropic, OpenAI, or Ollama.

The output includes BRINGYOUR-VALIDATE.md, which tells your agent what to review after import.

MCP

Local MCP lets Claude Code or Codex drive the same flows from inside the agent window.

claude mcp add bringyour -- /usr/local/bin/bringyour mcp
[mcp_servers."bringyour"]
enabled = true
command = "/usr/local/bin/bringyour"
args = ["mcp"]

Remote MCP at https://bringyour.ai/mcp is a no-data acquisition surface. It lets an agent discover Bring Your AI, run a minimal preview, and fetch local install commands. It does not accept GitHub handles, harness files, generated memories, user rules, API keys, or file contents.

Actual moves and first-setup builds run through the local CLI or local MCP server on the user's machine.

Buy lifetime access →
← back to bringyour.ai