CLI & TX Terminal

TaurusX has two terminal-based surfaces: the TX CLI (tx) and TX Terminal.

• tx — a standalone npm package you install globally and use from any terminal. Designed for developers, operators, and power users.
• TX Terminal — an embedded interactive session inside the Continuum Desktop interface. Same protocol, tighter UI integration.

Both surfaces share the same underlying API layer, device trust model, and Guardian safety enforcement. The CLI is documented here. TX Terminal is covered in Book 2.

# Requires Node.js 18+
npm install -g @taurusx/cli

# Verify installation
tx --version
# → tx v1.0.0

The CLI is available on macOS, Linux, and Windows. It requires Node.js 18 or higher. A native binary distribution (no Node.js required) is planned for TX v1.1.

TaurusX authenticates CLI sessions using a device trust model. Each device gets a unique signed credential tied to your account.

# Open browser OAuth flow and store device credentials
tx login

# Check who you're logged in as
tx whoami
# → Logged in as: you@example.com
# → Device: MacBook Pro 14" (device-id: abc123)
# → Linked at: 2026-05-14T10:32:00Z

# Revoke credentials and sign out
tx logout

Device credentials are stored in the OS keychain. They are never written to plain-text files. A refresh token allows silent re-authentication without re-opening a browser window for up to 30 days.

The CLI provides full access to your TaurusX agents and workflows — list, run, monitor, and stream logs without leaving your terminal.

# List all agents
tx agent list

# Dispatch an agent task
tx agent run my-agent "Summarise today's support tickets"

# Check task status
tx agent status run-abc123

# Stream live task logs
tx agent logs run-abc123

# List all workflows
tx workflow list

# Trigger a workflow
tx workflow run my-workflow

# Check workflow run status
tx workflow status wfrun-xyz789

tx ask and tx explain are the AI-powered commands — they bring the TaurusX Routing Engine to your terminal.

# Ask a question and get a plain-text answer
tx ask "What is the Guardian circuit breaker threshold?"

# Ask with piped context
cat server.log | tx ask "What caused this error?"

# Explain the output of a command
tx run df -h | tx explain "Explain this disk usage output"

# Explain a piece of code
cat main.go | tx explain "What does this do?"

tx ask is an alias for tx agent ask. Both commands use the same Routing Engine as the chat screen — including automatic state detection and tone adaptation. In terminal context, responses default to Precise tone: concise, code-first, no preamble.

The CLI exposes system health, mesh topology, and knowledge graph queries for operators and developers.

# Live system health dashboard
tx system status

# Runtime and version info
tx system info

# Show connected mesh nodes
tx mesh nodes

# Show mesh edge topology
tx mesh topology

# Search the knowledge graph
tx kg query "authentication middleware flow"

# Knowledge graph stats
tx kg stats

# Analyze an XR scene file
tx xr analyze path/to/scene.json

# List all XR scenes
tx xr scenes

tx status is a shorthand alias for tx system status.

Running tx terminal opens a full interactive terminal session routed through the TaurusX kernel. This is the CLI equivalent of the TX Terminal panel in Continuum.

# Open interactive TX Terminal
tx terminal

# Inside the session:
# $ ls -la
# $ git status
# $ ? How do I squash my last 3 commits?  ← ? prefix invokes Ask TX inline

Inside the TX Terminal session, prefix any message with ? to invoke Ask TX inline. The AI response appears directly in the terminal, formatted for the shell context — no markdown, code blocks in plain text, commands wrapped in the shell's copy format.