Terminal UI
The default way to use Aether is its terminal UI: a full-screen ACP client for chatting with project-local agents, reviewing tool progress, attaching files, changing settings, and resuming sessions.
aetherIf the current directory does not have .aether/settings.json, Aether starts onboarding first. After onboarding, the terminal UI launches against the same aether acp server used by editor integrations.
Features
Section titled “Features”- Streaming responses — See model output as it arrives with markdown and syntax highlighting.
- Tool tracking — Follow running tool calls and sub-agent progress.
- Plan visualization — View task/plan status updates emitted by tools.
- Inline diffs — Review file changes in a two-pane diff viewer.
- Slash commands — Trigger built-in commands and user-invocable MCP prompts with
/name. - File attachments — Attach files to prompts with the
@picker. - Settings overlay — Configure model, mode, reasoning, theme, and MCP server auth/status.
- Session resume — Resume previous ACP sessions.
UI layout
Section titled “UI layout”┌──────────────────────────────────────────┐│ Conversation ││ ├─ User messages ││ ├─ Agent responses (streaming markdown) ││ ├─ Tool calls (with progress) ││ └─ Plan entries ││ │├──────────────────────────────────────────┤│ Prompt input [@file] [/command]│├──────────────────────────────────────────┤│ agent · mode · model ░░░░ · 45% │└──────────────────────────────────────────┘The status line shows the active mode, model, reasoning effort, MCP state, and context usage. Segments are configurable in Wisp settings — see Settings & Themes.
When launched through aether, the terminal UI writes Wisp logs under /tmp/wisp-logs and uses RUST_LOG for verbosity.
RUST_LOG=debug aether