0x2ai-neme

NEME — the 0x2AI operating system

Multi-AI orchestration + crew chatroom + persistent memory. Single-Rust-executable MCP server with embedded React UI.

Install (Windows)

# 1. Install via npm globally
npm install -g @0x2ai/neme

# 2. Run installer (admin shell — writes to C:\0x2ai\)
neme install

# 3. Start bridge (foreground)
neme start

Bridge serves at http://localhost:3001/ — open in any browser to see the 0x2AI Code GUI.

CLI commands

neme install   Install bridge + skills + adapters to C:\0x2ai\ (requires admin)
neme start     Start bridge (foreground)
neme stop      Stop running bridge process
neme status    Show bridge process + port state
neme info      Print install paths and config

What gets installed

C:\0x2ai\
├── bin\bridge_spike.exe       Rust bridge binary (94MB, embeds GUI + MCP server)
├── db\sessions.db             SQLCipher-encrypted DB
├── anchors\seed-primals.js    identity-anchor seeder
├── skills\0x2ai-*             8 0x2AI slash-skill packs
├── config\bridge.env          BRIDGE_AUTH_TOKEN + SQLCIPHER_KEY + PORT + STRICT
├── adapters\
│   ├── claude-cli-plugin\     CC plugin shape (.mcp.json w/ live token)
│   ├── claude-desktop-mcpb\   MCPB scaffold (v2)
│   ├── cursor-config\         Cursor mcp.json snippet
│   └── raw-mcp-config\        reference for any MCP client
└── README.md

Connect an MCP client

After install, C:\0x2ai\adapters\ has client-specific snippets with your real auth token baked in.

• Claude Code (CLI): copy claude-cli-plugin\.mcp.json into your project root.
• Cursor: merge cursor-config\mcp.json into %USERPROFILE%\.cursor\mcp.json.
• Other MCP clients: see raw-mcp-config\.mcp.json for the wire shape.

Architecture

• Bridge binds to 127.0.0.1:3001 (loopback only, not network-exposed).
• MCP transport: HTTP at /mcp, token-gated via Authorization: Bearer ....
• DB: SQLCipher AES-256, key in config\bridge.env.
• Identity: STRICT_AGENT_IDENTITY=true requires authenticated agent writes.

Defender note

Win Defender real-time scanning may flag the unsigned bridge binary on first run. If neme install fails with file-vanished or quarantine errors, add Defender exclusion before retry:

Add-MpPreference -ExclusionPath C:\0x2ai, C:\Users\$env:USERNAME\AppData\Roaming\npm, C:\Users\$env:USERNAME\AppData\Local\npm-cache

v1.1 plans signed binaries to remove this friction.

Uninstall

npm uninstall -g @0x2ai/neme       # removes neme command
Remove-Item -Recurse C:\0x2ai\     # removes installed bridge + DB (admin)

Known v1 limitations

• Windows-only (macOS / Linux planned for v1.1+).
• No Win Service install — bridge runs as foreground process. Use neme start in a terminal you keep open.
• No auto-update — npm update -g @0x2ai/neme updates CLI; rerun neme install to refresh C:\0x2ai\bin\.
• MCPB submission to Claude Desktop is v2.