Chabeau - Terminal Chat Interface

Chabeau is a full-screen terminal chat interface that connects to various AI APIs for real-time conversations. Chabeau brings the convenience of modern chat UIs to the terminal with a focus on speed, ergonomics, and sensible defaults. It is not a coding agent.
See several of Chabeau's features in action in this short video.

Table of Contents
- Overview
- Feature Highlights
- Getting Started
- Working with Providers and Models
- Configuration
- Character Cards
- Personas
- Presets
- Appearance and Rendering
- Keyboard and Workflow Tips
- Architecture Overview
- Development
- License
Feature Highlights
- Full-screen terminal UI with real-time streaming responses
- Markdown rendering in the chat area (headings, lists, quotes, tables, callouts, superscript/subscript, inline/fenced code) with clickable OSC 8 hyperlinks
- Built-in support for many common providers (OpenAI, OpenRouter, Poe, Anthropic, Venice AI, Groq, Mistral, Cerebras)
- Support for quick custom configuration of new OpenAI-compatible providers
- Interactive dialogs for selecting models and providers
- Character card support (v2 format) with in-app picker and defaults per provider/model
- Persona system for defining reusable user identities with variable substitution support
- Reusable preset instructions with picker and CLI toggles for quick context switching
- Extensible theming system that degrades gracefully to terminals with limited color support
- Secure API key storage in system keyring with config-based provider management
- Multi-line input (IME-friendly) with compose mode for longer responses
- Message retry and message editing
- Slash command registry with Tab completion for faster command discovery
- Conversation logging with pause/resume; quick
/dumpof contents to a file - Syntax highlighting for fenced code blocks (Python, Bash, JavaScript, and more)
- Inline block selection (Ctrl+B) to copy or save fenced code blocks
- Prettified API error output with Markdown summaries for easier troubleshooting
For features under consideration, see WISHLIST.md.
Getting Started
Install
Authenticate
Launch
Inside the TUI, use /provider and /model to switch, and /help to see a full breakdown of commands and keyboard shortcuts.
Working with Providers and Models
Discover available options:
Manage authentication from the CLI:
Environment variables are used only if no providers are configured, or when you pass --env.
# Optional
Environment variable values can make their way into shell histories or other places they shouldn't, so using the keyring is generally advisable.
Configuration
Chabeau stores its configuration in config.toml.
- Linux:
~/.config/chabeau/config.toml - macOS:
~/Library/Application Support/org.permacommons.chabeau/config.toml
Generally, you can rely on the UI: when you use interactive commands like /model, /provider, /theme, or /character, press Alt+Enter (or Ctrl+J) to persist the selection.
Command-line helpers mirror those flows:
# Set default provider
# Set default model for a provider
# Persist a theme
# Set default character (per provider and model)
# Print the current configuration
Both the CLI and TUI run these mutations through the same configuration orchestrator. Chabeau caches the parsed file based on its last-modified timestamp, skipping redundant reloads when nothing has changed, and persists updates atomically so a failed write never clobbers your existing config.toml.
Prefer editing by hand? Copy examples/config.toml.sample to your config directory and adjust it to suit your setup. The sample covers provider defaults, markdown/syntax toggles, custom providers, custom themes, and character assignments.
Character Cards
Chabeau supports character cards in the v2 format, letting you chat with AI personas that define tone, background, and greeting. Cards can be JSON or PNG files (with embedded metadata).
Import and Manage Cards
Cards are stored in the Chabeau configuration directory. Use chabeau -c to print the directory name and any cards Chabeau discovers.
Use Characters in Chat
In the TUI, /character opens the character picker (↑↓ to navigate, Ctrl+O to inspect full definitions, Enter to select, Alt+Enter to set as default). You can also run /character <name> for quick switches.
Defaults and Directories
Set defaults for provider/model combinations via Alt+Enter (or Ctrl+J) in the picker, or on the CLI:
To use a separate cards directory, set the CHABEAU_CARDS_DIR environment variable before launching Chabeau.
Example cards live in examples/hypatia.json and examples/darwin.json.
Troubleshooting
- "Character not found": ensure the card is in
~/.config/chabeau/cards/(or its equivalent on macOS or Windows) or provide the full path. - "Invalid card format": verify the JSON structure matches the v2 spec with required fields (name, description, personality, scenario, first_mes, mes_example).
- "PNG missing metadata": PNG files must contain a
charatEXt chunk with base64-encoded JSON. - Cards not appearing in picker: check file permissions and ensure files have
.jsonor.pngextensions.
Format Reference
Character cards follow the v2 specification.
Personas
Personas allow you to define different user identities for conversations, each with their own name and optional biographical context. Unlike character cards (which define AI personas), personas define who you are in the conversation.
Configure Personas
Add personas to your config.toml:
[[]]
= "developer"
= "Alex"
= "You are talking to Alex, a senior software developer with expertise in Rust and distributed systems."
[[]]
= "student"
= "Sam"
= "Sam is a computer science student learning about AI and machine learning."
[[]]
= "casual"
= "Jordan"
# bio is optional - persona will just change the display name
Use Personas in Chat
In the TUI, /persona opens the persona picker (↑↓ to navigate, Ctrl+O to read the persona text, Enter to select). You can also run /persona <id> for quick switches, or select "[Turn off persona]" to return to anonymous mode.
When a persona is active:
- Your messages are labeled with the persona's name instead of "You"
- The persona's bio (if provided) is prepended to the system prompt
Variable Substitutions
Both personas and character cards support {{user}} and {{char}} variable substitutions:
{{user}}is replaced with the active persona's display name (or "Anon" if no persona is active){{char}}is replaced with the character's name (or "Assistant" if no character is active)
Persona vs Character Integration
Personas and character cards work together seamlessly:
- Character cards define the AI's personality, background, and behavior
- Personas define your identity and context in the conversation
- Both support
{{user}}and{{char}}variable substitutions - The persona's bio is added to the system prompt before the character's instructions
Presets
Presets let you inject reusable system instructions into the first and last system messages that Chabeau sends to the model. They are ideal for lightweight tone or formatting tweaks that you want to toggle quickly.
Chabeau ships with three built-in presets (short, roleplay, and casual) so you can experiment without editing your config. Set builtin_presets = false in config.toml to hide them from /preset, /preset <id>, and the --preset flag. If you define a preset with the same ID, your version overrides the built-in automatically.
Configure Presets
Add presets to your config.toml:
[[]]
= "focus"
= """
You are collaborating with {{user}}. Keep responses focused and direct.
"""
= """
Before finishing, list any follow-up actions.
"""
[[]]
= "roleplay"
= """
- Engage in roleplay with the user.
- Two paragraphs per turn max.
- Don't be shy to perform actions. Format these in italics, like this: *{{char}} frowns at {{user}}.*
- Be creative! Feel free to take the roleplay into new directions.
"""
pretext is wrapped in blank lines and prepended to the very first system message.posttext is wrapped in blank lines and appended to the final system message. If no system message exists at either position, Chabeau creates one automatically.- Presets support the same
{{user}}and{{char}}substitutions as personas and character cards.
Assign defaults per provider/model with default-presets:
[]
= "focus"
Use Presets in Chat
Launch with an ID like --preset focus, or pick interactively with /preset. Use Ctrl+O in the picker to review the preset instructions. The picker includes a "Turn off preset" option to clear the active preset.
The status bar shows the current preset when one is active so you can confirm the context you're using at a glance.
Appearance and Rendering
Themes
Chabeau ships with built-in themes and supports custom ones. Use /theme in the TUI to preview and Alt+Enter (or Ctrl+J) to persist the choice. On the CLI, run:
When no explicit theme is set, Chabeau tries to infer a sensible default from your OS preference (e.g., macOS, Windows, GNOME). If no hint is available, it defaults to the dark theme.
Custom themes belong in config.toml under [[custom_themes]]. See src/builtins/themes.toml for color references and examples/config.toml.sample for structure.
App messages—Chabeau’s own informational banners, warnings, and errors—use dedicated theme knobs so they’re easy to distinguish from assistant replies. Customize them with the app_info_*, app_warning_*, and app_error_* keys in your theme to control the prefix text, prefix styling, and message styling independently.
Markdown and Syntax Highlighting
Toggle these features at runtime:
/markdown on|off|toggle/syntax on|off|toggle
Chabeau persists these preferences to the config file automatically. Syntax colors adapt to the active theme and use the theme’s code block background for consistent contrast.
Color Support
Chabeau detects terminal color depth and adapts themes accordingly:
- Truecolor: if
COLORTERMcontainstruecoloror24bit, Chabeau uses 24-bit RGB. - 256 colors: if
TERMcontains256color, RGB colors are quantized to the xterm-256 palette. - ANSI 16: otherwise, colors map to the nearest 16 ANSI colors.
Force a mode when needed with CHABEAU_COLOR=truecolor|256|16.
Keyboard and Workflow Tips
Interface Controls
See the built-in help for a full list of keyboard controls. A few highlights:
- Alt+Enter (or Ctrl+J) to start a new line; Enter sends; Shift+arrow moves cursor in the input area.
- Compose mode (F4) flips the defaults: Enter inserts a newline, Alt+Enter/Ctrl+J sends, arrow keys stay in the input, and Shift+arrow scrolls the transcript.
- Tab autocompletes slash commands so you can discover options quickly.
- Ctrl+O opens the inspect view for picker items—providers include their ID, base URL, and auth mode; themes show their ID and every color override; character cards expand to the full v2 definition.
Mousewheel
Chabeau avoids capturing the mouse so selection operations (copy/paste) work as expected. Some terminals treat mousewheel events as cursor key input, so scrolling moves the conversation. Others reveal terminal history; in that case, use the cursor keys or PgUp/PgDn instead.
External Editor
Set the EDITOR environment variable to compose longer responses in your favorite editor:
# or vim, code, etc.
# VS Code with wait
Once set, press Ctrl+T in the TUI to launch the external editor.
Architecture Overview
Chabeau uses a modular design with focused components:
main.rs– Entry pointbuiltins/– Build-time assets embedded into the binarymodels.toml– Supported provider definitionsthemes.toml– Built-in UI themeshelp.md– In-app keyboard shortcut and command reference
cli/– Command-line interface parsing and handlingmod.rs– CLI argument parsing and command dispatchingmodel_list.rs– Model listing functionalityprovider_list.rs– Provider listing functionalitycharacter_list.rs– Character card listing functionalitytheme_list.rs– Theme listing functionality
core/– Core application componentsapp/– Application state and controllersmod.rs– App struct and module exportsactions.rs– Internal action definitions and dispatcher for chat loop updatesconversation.rs– Conversation controller for chat flow, retries, and streaming helperssession.rs– Session bootstrap and provider/model statesettings.rs– Theme and provider controllersui_state.rs– UI state management and text input helpers
chat_stream.rs– Shared streaming service that feeds responses to the app, UI, and loggersbuiltin_providers.rs– Built-in provider configuration (loads frombuiltins/models.toml)config/– Configuration data, defaults, caching, and persistencemod.rs– Public exports for configuration helpersdata.rs– Configuration data types and pure helpersorchestrator.rs– Cached config loader and mutation orchestratordefaults.rs– Default selection helpers andConfigimplementationsio.rs– Config path resolution and persistence routinesprinting.rs– CLI-facing config print helperstests.rs– Configuration module tests
message.rs– Message data structures
auth/– Authentication and provider managementmod.rs– Authentication manager implementationui.rs– Interactive prompts and input helpers for auth flows
character/– Character card support (v2 format)mod.rs– Module exports and public APIcard.rs– Character card data structures and v2 spec parsingloader.rs– Card file loading (JSON and PNG with metadata extraction)cache.rs– In-memory caching with invalidationservice.rs– Shared character cache and resolution helpers for the TUI and CLIimport.rs– Import command and validation logic
api/– API types and modelsmod.rs– API data structuresmodels.rs– Model fetching and sorting functionality
ui/– Terminal interface renderingmod.rs– UI module declarationschat_loop/– Mode-aware chat loop orchestrating UI flows, keybindings, and command routingevent_loop.rs– Async terminal loop orchestration, event polling, and stream dispatchlifecycle.rs– Terminal setup/teardown helpers and resource guardsmodes.rs– Mode-aware key handlers and text interaction utilities
layout.rs– Shared width-aware layout engine for Markdown and plain textmarkdown.rs/markdown_wrap.rs– Markdown renderer and wrapping helpers that emit span metadatarenderer.rs– Terminal interface rendering (chat area, input, pickers)osc_backend.rs/osc_state.rs/osc.rs– Crossterm backend wrapper that emits OSC 8 hyperlinkspicker.rs/appearance.rs/theme.rs– Picker controls and theming utilities
utils/– Utility functions and helpersmod.rs– Utility module declarationscolor.rs– Terminal color detection and palette quantizationeditor.rs– External editor integrationlogging.rs– Chat logging functionalityscroll.rs– Text wrapping and scroll calculationsclipboard.rs– Cross-platform clipboard helper
commands/– Chat command processing and registry-driven dispatchmod.rs– Command handlers and dispatcherregistry.rs– Static command metadata registry
Development
Running Tests
Performance
Chabeau includes lightweight performance checks in the unit test suite and supports optional Criterion benches.
- Built-in perf checks (unit tests):
- Short history prewrap (50 iters, ~60 lines): warns at ≥ 90ms; fails at ≥ 200ms.
- Large history prewrap (20 iters, ~400 lines): warns at ≥ 400ms; fails at ≥ 1000ms.
- Run with:
cargo test(warnings print to stderr; tests only fail past the fail thresholds).
- Optional benches (release mode) using Criterion 0.7:
- A
render_cachebench validates the cached prewrapped rendering path. - Run:
cargo bench - Reports live in
target/criterion/(HTML underreport/index.html). - To add new benches, create files under
benches/(e.g.,benches/my_bench.rs) and use Criterion’scriterion_group!/criterion_main!. - Benches import internal modules via
src/lib.rs(e.g.,use chabeau::...).
- A
License
CC0 1.0 Universal (Public Domain)