Skip to main content

Documentation Index

Fetch the complete documentation index at: https://handler.alduncanson.com/llms.txt

Use this file to discover all available pages before exploring further.

​
TUI and web UI

The TUI is the fastest way to explore an A2A agent when you want a live, interactive workflow instead of one command at a time.

​
Start the TUI

handler tui
You can also pre-connect on startup: 
handler tui --server demo
handler tui --server demo --server staging
handler tui --url http://localhost:8000
handler tui --bearer-env HANDLER_TOKEN

​
What the TUI is good at

  • switching between multiple agent connections in tabs
  • inspecting agent cards and supported capabilities
  • sending messages and watching streaming responses
  • editing auth, custom headers, and connection details interactively
  • keeping recent sessions close at hand while testing agents repeatedly
  • viewing logs without leaving the interface

​
Useful keyboard shortcuts

The default footer exposes the most important controls:
  • Ctrl+P opens the command palette
  • Ctrl+N opens a new server tab
  • Ctrl+W closes the active server tab
  • Ctrl+B switches to the previous server tab
  • Ctrl+T switches to the next server tab
  • Ctrl+M maximizes the focused panel
  • Ctrl+C quits the application

​
Connecting with saved servers

If you already defined named servers in servers.toml, the TUI can open them directly from the picker or from the command line with --server. This is usually the easiest way to work with mTLS or OAuth2 because the server definition already knows the URL and auth shape. See Servers and Authentication.

​
Auth in the UI

The auth panel supports the same major flows as the CLI:
  • bearer tokens
  • API keys
  • custom headers
  • mTLS certificate paths
  • OAuth2 client credentials
That makes the TUI useful for debugging an agent before you turn the same setup into a reusable named server.

​
Browser-hosted mode

If you want the same interface in a browser tab, serve it as a web app: 
handler web
handler web --port 9000
By default this binds to localhost:8001.

​
When to use the CLI instead

Prefer the CLI when you want scripting, JSON-friendly output, shell history, or repeatable task automation. See Messages, tasks, and sessions.