@vectara/io — io in your terminal

A Claude Code-style CLI for the Vectara platform. It drives io, the same assistant that powers the console's studio, over the public APIv2 — so everything you can do in the console (create and update agents, corpora, lambda tools, pipelines; run queries; diagnose sessions; design architectures) works from a terminal, with the same mediated-write safety model: io proposes, you approve, then the write executes.

npm install -g @vectara/io      # or: npx @vectara/io
io login                        # base URL + API key → ~/.config/vectara-io/
io                              # interactive TUI

What it does

• Interactive TUI (Ink): streaming replies, tool-call rows, markdown, slash commands, ctrl-c interrupts the running turn (twice quits).
• Approval cards: io's proposed writes render as cards — updates show a before/after diff against the live entity (the same PATCH-merge semantics the API uses). a approve, r reject, e edit the body in $EDITOR first.
• Questions: io's clarifying questions render as arrow-key pickers, with io's recommended option preselected; t types a custom answer.
• Console deep links print after every landed write.
• io preview <agent-key> (or /preview): a local, key-holding proxy server with a minimal chat page, so you can talk to any of your agents in a browser. Your API key never reaches the page.
• io design <agent-key> (or /design): the killer feature. Paste your Fable (Anthropic) API key once — it's registered as a Vectara BYO-LLM, never stored locally — and a Vectara-hosted design agent running on claude-fable-5 generates a self-contained web chat app for your agent. Files sync to ./io-design/<agent-key>/, served with live reload; iterate conversationally ("make it dark mode") and /io returns to the assistant. io design rotate-key / io design logout manage the registered key.
• Non-interactive: io -p "list my corpora" (or pipe stdin). Writes are rejected unless --auto-approve; progress goes to stderr, the reply to stdout. Exit codes: 0 ok, 1 turn error, 2 usage/auth.
• Sessions: io --resume / /resume replays the last session and rehydrates any approval the session stopped on; /compact compacts context; io sessions lists recent ones.

Auth

io login stores {baseUrl, apiKey} per profile in ~/.config/vectara-io/config.json (0600). VECTARA_API_KEY / VECTARA_BASE_URL / VECTARA_PROFILE override it. The CLI provisions its own copy of the io agent under the key io-assistant-cli (never touching the console's io-assistant) and stores your API key as that agent's CUSTOMER_VECTARA_API_KEY secret — the same trust model as the eval suite.

Development

io CLI is developed in Vectara's platform repository, where the assistant's definition is shared with the Vectara Console and bundled at build time — the CLI's io and the console's io are always the same assistant. See DEVELOPMENT.md in the source tree for contributor setup.