CLI Docs
nrx — the Norexus CLI.
The nrx CLI manages the local Norexus development stack, routes developer prompts, checks repo health, manages MCP tool attachments, and provides workspace chat access from the terminal.
The CLI is currently intended for internal and developer use. No public installer is published from this page.
nrx CLI is currently scoped to Norexus development workflows. Commands operate on your local stack and repos. No external API credentials are required for stack and repo commands. Workspace chat (nrx chat) requires an OpenRouter API key.
Stack commands
Manage the local Norexus development stack. Each service runs on a reserved port and logs to logs/stack/.
| Command | Description | Status |
|---|---|---|
| nrx stack up | Start all local stack services (Platform, Hotel, Auth, AI, Vault, Audit, Relations, API, CLI). Each service is spawned as a background process with its dev server. Logs stream to logs/stack/<service>.log. | Live |
| nrx stack up <service> | Start a single named service. Example: nrx stack up hotels. | Live |
| nrx stack down | Stop all running local stack services. | Live |
| nrx stack down <service> | Stop a single named service. | Live |
| nrx stack status | Print a table showing which services are running, their ports, and last-known process state. | Live |
nrx stack up
# Start only the hotel service
nrx stack up hotels
# Check what is running
nrx stack status
# Stop everything
nrx stack down
Repo commands
Inspect git state across all repos in the local Norexus workspace.
| Command | Description | Status |
|---|---|---|
| nrx repo status | Print a table of all repos: git attachment status, current branch, remote URL, and number of uncommitted changes. | Live |
Ping
Quick health check for running local services.
| Command | Description | Status |
|---|---|---|
| nrx ping | Send an HTTP ping to each running service and report response times and status codes. | Live |
| nrx ping <service> | Ping a single named service. | Live |
# Ping a single service
nrx ping hotels
MCP commands
Manage MCP (Model Context Protocol) server attachments for local AI tool sessions.
| Command | Description | Status |
|---|---|---|
| nrx mcp list | List currently attached MCP servers and their connection status. | Live |
| nrx mcp attach <name> | Attach a named MCP server from the preset configuration. Writes the attachment to the active AI tool config. | Live |
| nrx mcp detach <name> | Detach a named MCP server. | Live |
| nrx mcp auto | Auto-attach all MCP servers configured in config/mcp.json. | Live |
nrx mcp list
# Attach a specific server
nrx mcp attach supabase
# Detach a server
nrx mcp detach supabase
# Auto-attach all configured servers
nrx mcp auto
Chat
Terminal workspace chat via OpenRouter. Requires a user-provided OpenRouter API key (BYOK). No server-side key is stored.
| Command | Description | Status |
|---|---|---|
| nrx chat | Start an interactive chat session. You will be prompted for your OpenRouter API key on first run. The key is stored locally in the CLI config. | Live |
| nrx chat --model <id> | Start a chat session using a specific OpenRouter model ID. | Live |
nrx chat
# Use a specific model
nrx chat --model anthropic/claude-sonnet-4-5
Service names
Use these names when targeting a specific service with stack up, stack down, or ping.