Bring Your AI

Write behaviorSource files are read-only; target files are snapshotted before write; merge keeps existing Codex setup.

$ bringyour preview --from claude-code --to codex Claude Code found. Codex found. Move supported: yes Existing setup can be kept: yes Original files will not be changed. $ bringyour migrate --from claude-code --to codex --policy merge rollback snapshot: ~/.codex/.bringyour-snapshots/... validation: BRINGYOUR-VALIDATE.md

Bring Your AI separates the jobs buyers care about: moving an existing setup, syncing machines, distilling a safe snapshot, and creating a first one without staring at a blank rules file.

Move memories, rules, voice, workflows, MCP review notes, hooks, validation files, and session analytics artifacts.

Keep a central local hub without a hosted account.

Sync Claude Code, Codex, and Cursor through a local hub you can place in your own Git repo. Plans stay review-gated; platform-native config stays target-local.

Keep the useful parts, strip the risky parts.

Create a sanitized Claude, Codex, or Cursor harness bundle with redaction metadata and verification.

Turn public GitHub work history into a first Claude Code or Codex setup with confidence scores and source citations.

The CLI runs on your machine. Remote discovery and checkout do not accept your harness. Central sync uses a local hub by default, not a hosted account.

Generate an agent starter kit from public work history.

New users can turn public signals into a reviewed, confidence-scored setup for Claude Code or Codex.

bringyour preview --build --github you --to codex bringyour build --github you --to codex

Lifetime access while the product is young.

Every tier includes move, central sync, distill, build, validation, local CLI, local MCP, and no-data remote MCP discovery. Earlier buyers get the same toolkit for less.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

What Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.

CodeVF MCP lets AI hand off problems to real engineers instantly, so your workflows don’t stall when models hit their limits.

Client implementation for Mastra, providing seamless integration with MCP-compatible AI models and tools.

Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.

On-demand access to 150+ specialist AI agent templates — search, browse, and spawn agents. 150x reduction in context usage vs loading agents locally.

AgentChatBus is a persistent AI communication bus that lets multiple independent AI Agents chat, collaborate, and delegate tasks — across terminals, across IDEs, and across frameworks.

Remote MCP server (Streamable HTTP) at https://mcp.agenticrail.nz/ — deterministic step-order enforcement for AI agents. evaluate_step returns ALLOW or DENY before a step runs; verify_receipt proves a sequence's Ed25519-signed, hash-chained receipt chain is intact. No auth required: omit the bearer token and calls run on the public demo key. That first clause matters — the form has no "remote/hosted" field, and putting the endpoint in the description is the convention on that list ("Fully REMOTE! Just use…"). The rest mirrors your own server card verbatim, so the listing and the card can't drift.

An AI Agent with optional Human-in-the-Loop Safety and Model Context Protocol (MCP) integration.

Agent Mail Rooms is a paid remote MCP endpoint for OpenAI Codex agent coordination MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-