NtwineCLI
Every option, key and environment variable `npx ntwine` understands.
You can run npx ntwine from anywhere. One server serves every project on the machine, each with its own board, so if Ntwine is already running, a second run just joins it.
Where you run it decides what opens:
- In a folder that's already a project, you get that project's board.
- In a repository Ntwine hasn't seen yet, it asks whether to add it.
- Anywhere else, you get All projects.
npx ntwine [options]| Option | What it does |
|---|---|
--no-app | Print the URL without opening a browser |
--port <port> | Request a fixed port for a new server |
--sandbox | A disposable Ntwine to try things in: throwaway home and project, its own port, deleted when this terminal closes. Credentials (gh, cloudflared, Claude, Codex, the machine's ntwine.app key) are shared |
--link | Print a fresh single-use sign-in link for the running board |
--sessions | List the devices signed in to the running board |
--sign-out <id|all> | Sign one device out, or every one of them |
--status | Report the board running for this project: address, pid, version |
--stop | Stop the board running for this project; running agents keep going |
--debug | Stream the full event feed to the terminal instead of the compact readout |
-h, --help | Show help |
Keys in the terminal
While Ntwine is running, the terminal you started it from listens for two keys:
| Key | What it does |
|---|---|
| R | Set up remote access |
| L | Show a fresh single-use sign-in link as a QR code |
Environment
By default, Ntwine runs the Claude Code and Codex versions it pins. You can point it at your own build instead:
| Variable | What it does |
|---|---|
NTWINE_CLAUDE_BIN | Run this Claude Code build instead of the one Ntwine pins |
NTWINE_CODEX_BIN | Run this Codex build instead of the one Ntwine pins |