The Qorven TUI is built into the same binary that powers the gateway. Run qorven chat and you get a Discord-style terminal UI with slash commands, agent picker, tool calls, streaming tokens — everything the web UI has.

​
Run it

qorven chat                      # connect to local gateway
qorven chat --server https://...  # remote install
First run asks you to pick a Qor; subsequent runs remember.

​
What you get

  • Split pane — chat on the right, sidebar on the left with the current Qor, model, session stats
  • Streaming tokens — same UX as the web
  • Slash commands — /agent, /model, /tools, /compact, /help, 22 in total
  • Keyboard-first — every action has a key binding
  • Code mode — /code flips into a VS Code-style layout with file tree + editor panels
  • Agent picker — /agents opens a filterable list
  • Sessions — /sessions for other channels (email threads, group chats)
  • Theming — follows your terminal’s theme; purple accents adapt

​
Why use the TUI

You live on the command line

Same reason people use k9s or lazygit. The TUI is fast and stays in your flow.

You're SSH'd into a headless box

No browser, no port-forward, no hassle. The TUI works over SSH.

You want fewer tabs

If the web UI is one more browser tab you don’t need open, kill it.

You want to script interactions

TUI ↔ stdout. Pipe, automate, build CI around it.

​
Where next

Slash commands

Every /cmd and what it does.

Keybindings

Cheat sheet.

Code mode

VS Code layout in your terminal.

Agent picker

Switching between Qors fast.