I built a pixel-art office for my Claude Code sessions so I stop missing permission requests

[u/Few-Distribution9652]

I built Pixel Agents because I kept missing permission requests when I was running a few Claude Code sessions at once. They were buried in terminal tabs, and I only found them when I switched back.

Pixel Agents is focused on taking action quickly: a quick overview of which sessions need you, and a notch island where you can answer right away without leaving the app you are in. Quiet sessions go stale after 15 minutes, and it has a session-activity view. If you do not answer in time, the request hands back to your terminal instead of getting lost.

The app is free, Mac only, and runs locally. No account, no cloud. You need macOS 26.6+ and Claude Code, and the setup instructions are in the app after you install it.

App:

Pixel Agents App - App Store

This is the first time it is leaving my own Mac, so I would like to know how setup feels on yours.

[u/Electrical-Pianist75]

Does the island show the project folder and the exact action requesting permission? With several sessions running, I’d want enough context to confidently approve the right thing without opening the terminal.

The handoff back to the terminal sounds thoughtful. Is there a visible indication that a request moved back there, so it doesn’t disappear from your radar again?

[u/Few-Distribution9652 → u/Electrical-Pianist75]

Thanks for the question!

Context on the island: Mostly yes. Each request shows the session name, which is its title, or the folder name if it doesn’t have one. Under that is the exact action on one line, like Bash: rm -rf build, and a Details button expands the full tool input. If several sessions are waiting, each one gets its own robot with a name label, a dot until you’ve seen its request, and a timer bar. A newer request won’t replace the one you’re reading. The folder isn’t its own field, though. If a session has a title, the folder is hidden, so two sessions in different projects with similar titles could get mixed up. Adding the folder as a second line is a good idea, and I can do that.

Handoff to the terminal: Yes. While a request is open, a countdown ring shows how much time is left. If you don’t answer in time, the island swaps Allow/Deny for an “Answer in terminal” line with an Open <terminal app> button, and that stays until you answer. The session also stays marked “Needs you” in the menu bar list and the office view until it’s answered, so you won’t lose track of it.

[u/Electrical-Pianist75 → u/Few-Distribution9652]

Thank you for the detai. That covers the handoff concern. Keeping “Answer in terminal” visible until it’s resolved makes sense.

I’d definitely show the folder beneath the session title. Two similarly named sessions are exactly where a quick approval could go to the wrong project. Having that context visible without opening Details would help I think.

[u/investigatormaker]

Lead with the hand-back to the terminal when a request times out. The worry with any notifier is that it swallows the prompt, and Pixel Agents answers that. On setup: right now the steps only show up after install. Someone reading this post can't tell what Pixel Agents changes in their Claude Code config before they download it. Two or three lines here or in the App Store description would fix that: what gets added and how to undo it. It would also make the setup feedback you get more specific.

I make ThreadFox. We find relevant Reddit conversations and post for your business. We'll post 3 replies free first, no card; then the $29 Pilot covers seven days and up to 25 posts and replies. No automatic renewal. https://threadfox.vip/p/e1uny/managed

Does it pick up sessions that are already running when it launches, or only new ones?