talis-cli 0.1.0a9

Command-line client for the Talis trading platform. Sign in via device flow, manage sessions, view portfolio, place orders.

talis-cli

Command-line client for the Talis trading platform.

pip install talis-cli

talis login                  # device flow — opens a browser, you approve
talis approve ABCD-EFGH      # approve another login from this signed-in CLI
talis whoami                 # shows current session
talis portfolio              # balance + open positions

talis buy BTC-USD 25         # market buy $25 of BTC
talis close BTC-USD          # close 100% of the BTC position

talis outcome list           # browse live HIP-4 outcome (prediction) markets
talis outcome buy 100 yes 11 # buy $11 of the YES side of outcome 100 (#1000)
talis outcome close 100 yes 25  # sell 25 YES shares of outcome 100

talis sessions               # list active sessions (Connected Devices)
talis sessions revoke ab12   # revoke a session by short prefix
talis logout                 # revoke the current session

By default the CLI targets AWS production at https://api-aws.jarvis.trade. Set TALIS_ENV=render only when intentionally auditing the legacy Render deployment, or set TALIS_API_URL to override the endpoint completely.

Read-only sessions

For automation, scripts, or letting an LLM browse your account without authority to trade, request a read scope at login:

talis login --read-only

Read-scope sessions are denied (403) on every endpoint that mutates orders, positions, strategies, or wallets — enforced server-side at the API layer. When approving a login with talis approve, the approving session's scope is also enforced: a read-only session can only approve read-only CLI access.

Output mode

When stdout is a TTY (interactive shell), commands render with rich formatting. When stdout is piped or redirected, commands emit one JSON object per line — suitable for parsing from scripts or LLM agents. Force JSON anywhere with --json.

Credentials

The CLI stores its session token at ~/.talis/credentials with chmod 600 on POSIX systems. The token is a JWT; treat it like any other credential.

Relationship to cli/jarvis_cli.sh

The bash script at cli/jarvis_cli.sh is the legacy engineer power tool — admin-keyed, POSIX-only, prose output. It still works and isn't going anywhere short-term.

talis-cli is the going-forward client. All new features (device-flow auth, per-user credentials, JSON output, scope-aware sessions, future commands) land here. The bash CLI will be archived once talis-cli reaches feature parity for admin/engineer workflows.

If you're a Talis engineer with the admin API key, you can keep using either. If you're a public user or driving the API from an LLM / script, use this one.

Status

Alpha. APIs may shift. File issues at the Talis trading engine repo.

MCP (Model Context Protocol)

talis mcp runs a stdio MCP server that exposes your Talis account as typed tools — any MCP client (Claude Code, Claude Desktop, other agents) can read your portfolio, pull Talis Research, place paper trades, create strategies, set price alerts, and talk to the Talis chat agent. Log in first (talis login); the server authenticates as the logged-in user.

Add it to Claude Code:

claude mcp add talis -- talis mcp

Or to Claude Desktop (and other clients using the mcpServers config shape) — claude_desktop_config.json:

{
  "mcpServers": {
    "talis": {
      "command": "talis",
      "args": ["mcp"]
    }
  }
}

Tools: whoami, portfolio, balance, research, packets, brief_latest, history, buy, sell, close, create_strategy, chat, notifications_create.

Safety: the trading tools (buy / sell / close / create_strategy) default to paper=True — an isolated simulated book. An agent must pass paper=False explicitly to trade real money. Set TALIS_PAPER=1 in the server's environment to force paper mode regardless of tool arguments. Withdrawals and wallet creation are not exposed over MCP. For a strictly read-only agent, log in with talis login --read-only — the server rejects every mutation at the API layer.