Command history

Every command you run is remembered, and there are three ways back to one: the ↑/↓ arrows, ghost-text suggestions as you type, and the Ctrl+R picker. You can also double-click a past prompt line (❯ <command>) to run it again. A single click does nothing, and drag-selecting its text still just copies.

Arrow-key recall

↑ walks backward through the current tab's history, most recent first; ↓ walks forward again. If you've already typed a command before pressing ↑, stepping forward past the newest history entry restores that unexecuted text instead of losing it. Each recalled command and restored draft lands on the input line with the cursor at the end, ready to edit or run.

Ghost text

When what you've typed is the prefix of a past command, the rest of the most recent match appears after the cursor as greyed ghost text:

Press → or End at the end of your typed text to accept the whole suggestion. Any other key leaves it alone — keep typing and the suggestion narrows or disappears. Matching is case-sensitive, and ghost suggestions draw on your history from all tabs and previous runs, so a command you typed anywhere can complete everywhere.

The Ctrl+R picker

Ctrl+R (or the hist command) opens a window listing the tab's recent commands, most recent at the bottom, just above the command bar:

↑/↓ move the selection, Return runs the selected command, Escape closes without running anything. A row can also be clicked. With no history yet, the window shows (no history).

What's kept, and where

History is per-tab: each tab records its own commands (up to 100; older entries fall off), and that's what arrow-key recall and the picker show. Running the same command twice in a row stores it once. Per-tab history persists with the agent's state, so it survives janus --relaunch.

There's also a global history spanning all tabs and all runs, capped at 1000 entries and stored in your home directory — that's what ghost text draws from. The split is deliberate: recall and the picker answer "what was I doing in this tab," while ghost text answers "how did I last type this command anywhere."

Global-history updates replace the stored file atomically, so an interrupted or failed write leaves the previous valid history available. If the file is malformed or cannot be read or written, the server log reports warning: global command history unavailable: <reason> once. Repeated failures stay quiet until a read or write succeeds; a later failure can then report a fresh warning.