Nixie

Whitepaper · v0.1 draft · November 2026

Nixie.Your code, your model.

Nixie is an AI coding agent that runs on your machine, talks to the model provider you choose with your own API key, and shows every step in an orange CRT terminal. It ships as a CLI, a desktop app and an MCP server. $NIXIE is the access key: holders unlock Nixie with one wallet signature. Nixie never receives your code, your prompts or your model key, and never holds or moves your tokens.

01Why Nixie

Most coding agents tie you to one vendor: their model, their subscription, their servers in the middle of your code. Nixie takes the opposite position. You pick the model, you pay the provider directly at its own prices, and the agent runs where your code already is.

The second idea is the screen. Nixie tubes were vintage displays whose digits glowed orange; the Nixie terminal is a CRT-style interface in that glow, where every file read, edit and command is drawn as it happens and every risky step waits for your yes.

02What ships

SurfaceWhat it isStatus
CLInixie starts the agent in a folder and opens the terminal in your browser; nixie -p runs one prompt as plain text for scripts.On npm as nixie-code
DesktopThe same agent and terminal in its own window. Updates itself from GitHub Releases.Windows installer
MCP serverClaude Code, Cursor or Claude Desktop hand a task to nixie_task and get back the reply, the files changed and the commands run.In nixie-code
Web demoThe terminal in the browser with labelled DEMO replies, free for everyone. Holders can go live in a private, temporary cloud sandbox.Demo live; live sandboxes rolling out

All of them share one agent core, so a task behaves the same whichever way you start it.

03How the agent works

Nixie runs a streaming tool-use loop: the model answers, asks for tools, gets the results, and repeats until it is done or reaches a step limit (50 by default). Every event goes to one stream that the terminal, the plain-text printer and MCP all read.

ToolDoesAsks first by default
list_filesLists files by patternNo
read_fileReads a file or a line rangeNo
searchSearches text across the projectNo
git_diffShows what changed in the project's git working treeNo
edit_fileReplaces an exact piece of a file, shown as a diffYes
write_fileCreates or overwrites a fileYes
run_commandRuns a shell command in the project, with a timeoutYes
  • Workspace: the folder Nixie starts in. File paths that leave it are refused, symlinks included.
  • ask (default): every edit and every command needs your yes. auto-edit: edits run, commands still ask. full: nothing asks, with a warning at start.
  • A permission prompt shows the exact diff or command, with Yes, No or Always for this session.
  • Only you can choose full, from the config, the terminal or a CLI flag. Never the model, never an MCP caller.
  • Sessions are saved locally and can be resumed. A NIXIE.md file in the project adds your own instructions.

04Bring your own key

Nixie works with Anthropic, OpenAI, Google Gemini, OpenRouter, and Ollama or any OpenAI-compatible endpoint. You choose the provider and model; there is no Nixie model and no Nixie bill.

DataWhere it goesNever goes to
Your code and promptsYour machine and the model provider you choseNixie's servers
Your model keyYour machine (env, a user-only config file, or the desktop app's encrypted store) and your providerNixie's servers
Your wallet address and one signatureThe Nixie login server, once per loginAnywhere else
Your private wallet keyNowhere: your wallet signs, Nixie only reads the signatureNixie, ever

Live web sandboxes are the one place Nixie runs for you in the cloud. There the key goes from your browser straight to your own sandbox, stays in its memory, and is deleted with the sandbox; the website never sees it.

05Holder access

The CLI, the desktop app, the MCP server and live sandboxes open for wallets holding at least $10 of $NIXIE. The web demo stays free.

  • nixie login (or /login in the terminal) shows a short code and opens the login page.
  • You connect your wallet and sign a Sign-In with Ethereum message (EIP-4361). It costs no gas and approves nothing.
  • The server checks the code, the signature and your $NIXIE balance on Robinhood Chain against the minimum.
  • If it passes, the server issues a signed pass (ES256 JWT) valid for 24 hours. Your copy of Nixie checks that signature with a public key built into it before every turn.
  • The balance is checked again at every new login and for every new live sandbox.

An honest limit: the agent and the model run on your machine, so someone who patches their local copy can skip the check. The gate protects access to the product and its terminal, not a model. We chose that over sending your code through our servers.

06The $NIXIE token

$NIXIE is a token on Robinhood Chain. Its one job in the product is access: holding at least $10 worth of it unlocks Nixie. Contract: To be announced.

  • Holding is checked with a signature, never a transaction, a deposit or an approval.
  • Nixie never holds, locks, stakes or moves your tokens, and never asks for your private key.
  • The $10 is valued at the DEX price at the moment you log in (DexScreener, with GeckoTerminal as a fallback). A thin market can move that price, so the minimum is a convenience, not a guarantee.
  • The minimum, the chain and the contract address are server settings; the address is set from the site's admin page. They can change without a new release, because the pass carries the result, not the rule.
  • $NIXIE carries no promise of value, yield, revenue share or future features. It is not an investment product.

Before launch the contract address reads 'To be announced'. It appears here and in the site footer as soon as it is set.

07Security and privacy

  • Non-custodial: no Nixie server or model ever holds a wallet key, signs or sends a transaction.
  • The local terminal server listens on 127.0.0.1 only, behind a random per-launch token and a strict Host and Origin check, so other websites cannot drive the agent.
  • MCP callers are capped at auto-edit: they can never switch on full, and commands still ask you.
  • Shell commands are not sandboxed by the operating system on your machine. That is why commands ask by default, and why full is a choice only you can make.
  • Live sandboxes are private to one wallet, last at most 15 minutes, stop on their own when idle, and are deleted with everything in them.
  • The desktop installer is not code-signed yet, so Windows may warn on first run. Updates are checked against the release's SHA-512 hash.

08Status and next steps

AreaTodayNext
LoginEarly preview: the login site is not live; the dev gate is documentedLogin site live, then the dev gate leaves the docs
WebFree demo with DEMO repliesLive holder sandboxes in the cloud
DesktopWindows, unsignedCode signing; other platforms are not planned yet
TokenMinimum: $10 of $NIXIE; contract to be announcedContract address published at launch, on Robinhood Chain mainnet

Plans change. Nothing in this section is a promise or a commitment to a date.

09Disclaimer

Not financial advice. $NIXIE carries no promise of value. Not affiliated with Robinhood Markets, Inc. Nixie is software that edits files and runs commands on your behalf when you allow it; review what it does, especially in full mode.

Install Nixie · Back to Nixie

Nixie whitepaper