Configuration and themes
Start with Settings for appearance, sessions, keyboard preferences, and integrations. For file-based configuration, edit ~/.config/raven-term/config.toml. The defaults work without a config file.
The config file
# ~/.config/raven-term/config.toml — everything optional
font_size = 13.0
font_family = "JetBrainsMono Nerd Font Mono"
scrollback_lines = 10000
padding = 2.0
# launch something other than $SHELL in new panes
# program = ["ssh", "devbox"]
restore_session = true # persist spaces/panes across restarts
resume_agents = true # respawn claude/codex by resuming sessions
[colors] # per-color overrides on top of the theme
# background = "#0b0b10"
# ansi = ["#...", ...] # 16 entries: 0-7 normal, 8-15 bright
[[projects]] # per-machine worktree environments
root = "~/code/myapp"
[[projects.up]]
name = "web"
command = "npm run dev"Themes
Built-in themes, switchable live from Change theme… (⌘K, or ⌘⌥T); a theme of your own is made in the Theme Studio. The selection is stored in ~/.raven/work-ledger.db, which every Raven surface reads; [colors] overrides in the TOML apply on top of whichever theme is active.
Keyboard shortcuts
- ⌘DSplit the focused pane (BSP)
- ⌘TNew space
- ⌘WClose pane
- ⌘⇧[⌘⇧]Previous / next space
- ⌘1–9Jump to space
- ⌘KCommand palette
- ⌘⇧ENotes pane
- ⌘⇧PPull request pane
- ⌘C⌘VCopy / paste (bracketed)
- ⌘⇧VPaste as one line (joins newlines with spaces)
- ⌘clickOpen hyperlink (OSC 8)
These are the defaults. Settings (⌘,) chooses the space-shortcut scheme. To add bindings, key sequences, and keyboard modes, put JavaScript in init.js beside your config file. Explicit user shortcuts keep their precedence. The automation guide shows how to register an action, bind it, and reload without restarting terminals.