Skip to main content
TX-DSS v1.0

Book 2

Terminal TX

Power, with guardrails.

Back to Documentation

Overview

TaurusX provides two terminal experiences: TX Terminal, an interactive session embedded inside the Desktop Continuum interface, and the TX CLI (tx), a standalone command-line tool you install in your own terminal.

Both surfaces share the same underlying kernel protocol, device trust model, and safety architecture. The difference is context: TX Terminal is tightly integrated with the OS UI, while the CLI is a portable tool for developers and power users.

Terminal surfaces are restricted to Tier 3 accounts (18+). Kids Mode accounts (Tier 1 and Tier 2) cannot access TX Terminal or the CLI.

TX Terminal

TX Terminal is an interactive session panel built into the TaurusX Desktop Continuum interface. It provides a full shell-like experience with TaurusX kernel integration, real-time AI assistance, and safety enforcement.

Key capabilities:

  • Kernel-routed execution — commands run via the TaurusX execution kernel, not raw shell
  • AI-assisted input — Ask TX is available inline; prefix a message with ? to get AI help
  • Session context — TX Terminal maintains working directory, environment variables, and command history across reconnects
  • Guardian-enforced boundaries — destructive or high-risk commands require explicit confirmation

TX Terminal is accessible from the Continuum sidebar under Terminal. It opens in a full-screen panel with a split view option for running commands alongside the chat screen.

TX CLI (tx)

The tx CLI is a Node.js-based command-line tool that brings TaurusX to your existing terminal. Install it once, link your account with tx login, and use TaurusX from any terminal session.

bash
# Install globally
npm install -g @taurusx/cli

# Check version
tx --version

# Log in and link your device
tx login

# Verify your session
tx whoami

The CLI communicates with the TaurusX OS Backend API using short-lived device-scoped tokens. All requests are authenticated, rate-limited, and audited.

Login & Device Trust

TaurusX uses a device trust model for CLI authentication. When you run tx login, the following flow occurs:

  1. Your browser opens the TaurusX OAuth page.
  2. You authenticate with your TaurusX account (email, SSO, or social login).
  3. A device grant token is issued and stored securely in your OS keychain.
  4. A refresh token allows silent re-authentication without re-opening a browser.
CommandDescription
tx loginOpens browser OAuth flow and stores device credentials
tx logoutRevokes device grant and removes stored credentials
tx whoamiShows linked account email and current device ID
Device grants are stored in the OS keychain (macOS Keychain, Windows Credential Manager, or ~/.taurusx/credentials on Linux). They never touch plain-text config files.

Ask TX

tx ask (also available as tx agent ask) lets you ask TaurusX a question directly from the command line and get a plain-text answer.

bash
# Ask a one-shot question
tx ask "What is the Guardian circuit breaker threshold?"

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

# Use tx explain to parse command output
tx run df -h | tx explain "Explain this disk usage"

Ask TX uses the same Routing Engine as the chat screen. The response tone and detail level are adapted to the terminal context — concise by default, with full detail available on request.

Safety Model & Sandbox

Both TX Terminal and the CLI operate within the TaurusX safety architecture. The Routing Engine classifies every command before execution and applies one of three policies:

Risk LevelPolicyExample Commands
LowExecute immediatelyls, pwd, cat, grep
MediumExecute with audit log entryrm file, git push
HighRequire explicit confirmation promptrm -rf /, DROP TABLE
BlockedRefuse execution, explain reasonCommands that bypass Guardian

The sandbox ensures that even if a command is executed, its blast radius is limited to the current working directory and session scope unless the user has explicitly granted broader permissions.

You can inspect why a command was classified at a particular risk level by running tx explain "command" before executing it.

Command Reference

CommandSubcommandDescription
tx loginAuthenticate and link this device
tx logoutRemove saved credentials
tx whoamiShow linked account and device
tx agentlistList all configured agents
tx agentrun <id> "goal"Dispatch an agent task
tx agentstatus <run-id>Check task status
tx agentlogs <run-id>Stream task logs
tx workflowlistList all workflows
tx workflowrun <id>Trigger a workflow
tx systemstatusLive system health
tx systeminfoRuntime info
tx meshnodesNode map
tx meshtopologyEdge topology
tx kgquery "text"Search knowledge graph
tx kgstatsKnowledge graph stats
tx xranalyze <file>Analyze XR scene
tx terminalOpen interactive TX Terminal session
tx run <cmd>Run a command via TaurusX Kernel
tx ask "prompt"Ask TX Intelligence
tx explain "text"Explain output in plain language (AI)