CLI Usage
The neusiscode binary runs in two modes: an interactive TUI (the default) and a non-interactive run command for one-shot prompts and scripting.
neusiscode # Start the TUI
neusiscode /path/to/dir # Start the TUI in a specific directory
neusiscode -c # Continue the last session
neusiscode -s <id> # Continue a specific session
neusiscode run "prompt" # Run a single prompt (non-interactive)
The TUI
Running neusiscode with no subcommand starts the terminal UI. An optional positional path opens it in that directory.
| Flag | Alias | Description |
|---|---|---|
--continue | -c | Continue the last session |
--session <id> | -s | Continue a specific session |
--fork | Fork the session when continuing (use with -c or -s) | |
--model <provider/model> | -m | Model to use, e.g. neusiscode/auto |
--agent <name> | Agent to use | |
--prompt <text> | Seed the session with an initial prompt |
The run command
run sends a prompt to a session and streams the result to your terminal, then exits when the session goes idle — useful for scripting and CI.
neusiscode run "explain what this repo does"
neusiscode run -c "now add tests" # continue the last session
neusiscode run --format json "summarize" # raw JSON events for tooling
echo "review this" | neusiscode run # read the prompt from stdin
Options
| Flag | Alias | Description |
|---|---|---|
--continue | -c | Continue the last session |
--session <id> | -s | Session id to continue |
--fork | Fork the session before continuing (requires -c or -s) | |
--model <provider/model> | -m | Model to use, e.g. neusiscode/auto |
--agent <name> | Agent to use | |
--command <name> | Run a slash command; the message becomes its arguments | |
--format <default|json> | Output format. json streams raw events | |
--file <path> | -f | Attach one or more files to the message (repeatable) |
--title <text> | Title for the session (truncated prompt if no value) | |
--variant <name> | Model variant, e.g. reasoning effort high, max, minimal | |
--thinking | Show thinking blocks | |
--interactive | -i | Run in direct interactive split-footer mode |
--replay | Replay visible session history on interactive resume | |
--replay-limit <N> | Cap visible interactive replay to the newest N messages | |
--dangerously-skip-permissions | Auto-approve permissions that are not explicitly denied |
The prompt can also be piped in over stdin. If you pass both a message argument and piped input, they are concatenated.
:::info Neusis Cloud
Neusis Code ships with Neusis Cloud as its default provider — access to coding models with a single API key. The default model is neusiscode/auto, which lets the proxy pick the concrete model for the session; the specific model ids stay selectable with -m. Get a key at https://neusis.ai. When you hit the free usage limit, Neusis Code surfaces a Free usage limit reached message inline rather than prompting an upgrade.
:::
Interactive split-footer mode
--interactive (-i) launches a direct interactive mode with a split footer — you keep typing follow-up prompts in the same view instead of running one prompt and exiting.
neusiscode run -i
neusiscode run -i -c # resume the last session interactively
--interactive requires a TTY on stdout. It cannot be combined with --command or --format json.
Session-history replay on resume
When you resume a session interactively, pass --replay to print the visible history first, so you can see the conversation so far before continuing:
neusiscode run -i -c --replay
neusiscode run -i -s <id> --replay-limit 20
--replay and --replay-limit only apply with --interactive, and replay happens when you resume an existing session (with -c or -s, and not --fork). --replay-limit takes a positive integer and shows only the newest N messages.
Shell mode in the prompt
Inside interactive mode, type ! at the start of an empty prompt to switch the input into shell mode and run a command directly. The placeholder changes to Run a command... "git status". Press Escape, or Backspace on an empty line, to return to the normal prompt.
Notes
The web, share, and serve commands from upstream OpenCode are not part of Neusis Code — sessions stay local to your machine and there is no built-in sharing or hosted-server surface.
See also Commands for built-in and custom slash commands, and Keyboard Shortcuts for in-TUI keys.