NixieOpen cloud agent

Install Nixie. Three ways in.

Run Nixie on your own projects as a CLI, from your MCP host, or as a desktop app. Every way uses your own model key.

Before you start

  • Node.js 20.19 or newer, for the CLI and MCP.
  • A key from Anthropic, OpenAI, Google or OpenRouter, or Ollama running locally (no key needed).
  • A wallet holding $NIXIE, checked once with a signature: no gas, no approval.

Early preview: the wallet login site is not live yet, so nixie login cannot unlock Nixie for now. Until then, start the CLI and MCP server with NIXIE_DEV_GATE=1, as shown below.

CLI

The orange terminal in your browser, started from your project folder.

  1. Install

    npm install -g nixie-code

    The command is nixie.

  2. Log in with your wallet

    nixie login

    Opens the login page; sign the message in your wallet. Early preview: skip this step for now.

  3. Start it in your project

    cd your-project
    nixie

    The first run asks for your model key; it stays on your machine. In PowerShell the preview line is $env:NIXIE_DEV_GATE=1; nixie

    Early preview, with the dev gate:

    NIXIE_DEV_GATE=1 nixie
  4. Or set the key beforehand

    nixie config set-key anthropic

    Reads the key from stdin. ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_GENERATIVE_AI_API_KEY and OPENROUTER_API_KEY work too.

  5. One prompt, no UI

    nixie -p "fix the failing test"

    Prints the result and exits. Add --mode ask|auto-edit|full or --provider <p> --model <id> for one run.

MCP

Let Claude Code, Cursor or Claude Desktop hand tasks to Nixie. Tools: nixie_task and nixie_status.

  1. Claude Code

    claude mcp add nixie -- npx -y nixie-code mcp

    Early preview, with the dev gate:

    claude mcp add -e NIXIE_DEV_GATE=1 nixie -- npx -y nixie-code mcp
  2. Cursor or Claude Desktop

    {
      "mcpServers": {
        "nixie": {
          "command": "npx",
          "args": ["-y", "nixie-code", "mcp"],
          "env": { "NIXIE_DEV_GATE": "1" }
        }
      }
    }

    Add it to ~/.cursor/mcp.json, or to claude_desktop_config.json from Claude Desktop's Settings, Developer, Edit Config. Drop the env line once the login site is live and you have run nixie login.

  3. What an MCP task may do

    An MCP task never runs above auto-edit: it can edit files, and every command still asks you first. Keys come from the env block or nixie config set-key.

Desktop

The same terminal in its own window, for Windows. It updates itself.

  1. Download the installer

    Get Nixie-Setup-<version>.exe from the latest release on GitHub and run it. It installs for your user only.

  2. If Windows SmartScreen warns

    The installer is not code-signed yet. Choose More info, then Run anyway.

  3. Open a project and add your key

    Pick a folder, then paste your model key when Nixie asks. The app keeps it encrypted with Windows' own key storage.

  4. Log in

    Type /login in the command line and sign with your wallet; a login lasts 24 hours. Early preview: this works once the login site is live.