Aulora
One terminal workspace for every Claude Code session you run.
- Years
- 2026
- Type
- Personal
- Discipline
- Backend, AI
- Stack
- Rust, Ratatui, Claude Code
If you run Claude Code in several projects at once, you end up with a VS Code window per project, mostly to hold Claude's terminal. Aulora replaces those windows with one terminal workspace that tracks every session through Claude Code's hooks.
It's a Rust workspace with a core crate (model, protocol, reducer, transcript reader), a daemon that owns the PTYs, and a Ratatui dashboard. Everything stays on your machine.
What I did
- 01Daemon-owned PTYs, so sessions survive closing the UI, and `aulora attach` opens any pane in another terminal
- 02Hook-driven session state: working, waiting on permission, asking a question, or done
- 03Changes view with per-agent attribution read from session transcripts
- 04gitignore-aware file tree, fuzzy file finder, and ripgrep-engine search
- 05A VS Code extension to prompt sessions running in editor terminals
(Inside)
01
What needs you
Permission prompts, questions, and plans waiting for review turn the agent red in the sidebar. n jumps straight to the next one.
02
What changed, and who changed it
A source-control view with syntax-highlighted diffs and a coloured dot for the Claude session that wrote each change, read from its transcript.
03
Real terminals, owned by a daemon
Claude Code and your shells run in panes that keep running after you close the dashboard. Each shell's status shows whether its dev server is running, crashed, or exited.