I usually have four or five Claude Code sessions running across projects. That meant a pile of terminals, and the one waiting for permission was always at the bottom. So I built Horadric. Each session becomes a small tile on the edge of the screen, grouped by project. It shows what the agent is doing, for how long, and how full its context is. When a session needs you, the tile turns amber. Click it and you get the real Claude Code CLI in a terminal. No chat UI wrapped around it. A few other things: Ctrl+Alt+Space from anywhere jumps to the session that has waited longest A Windows notification when a session starts waiting and you’re looking elsewhere Plain terminals and a browser pane beside the agents, and the agents can drive the browser Your 5-hour and weekly limit usage, and switching between Claude subscriptions with sessions resuming on the new account Sessions survive a crash, an update or a reboot A quest log per project: a Markdown checklist where clicking an item starts a session on it How Claude Code was used: it wrote almost all of it. I did the product direction, the design calls and the testing. It’s pure Rust drawing straight to Win32 and Direct2D, about 45 MB with four sessions open. Raw Win32 is not something I’d have taken on by hand. What I learned: Claude Code’s hooks are what make this possible. Horadric knows a session’s state from hooks in your settings, not from scraping terminal output. And keeping the real CLI as the UI meant I never had to chase Claude Code’s own updates. Free and MIT licensed. Windows 10 and 11. Also works with Codex and Grok Build. Site: https://horadric.dev/ Source: https://github.com/Mopra/horadric.dev Builds aren’t code signed yet, so SmartScreen will warn you the first time. submitted by /u/PR4DE
Originally posted by u/PR4DE on r/ClaudeCode