Yesterday a small open source build showed up on r/PromptEngineering. It is called Openbar, and it fixes a problem anyone running several coding agents at once knows well.
What’s new
The author runs Claude Code, Codex and Gemini CLI at the same time, each on its own task. Their point is that the prompts were never the hard part. The hard part is noticing the moment one agent stops and asks you something. You are deep in another window, and the agent just sits there waiting for a yes or no.
If you have ever come back to a terminal tab after twenty minutes and found an agent frozen on a single permission question, you know the cost. The agent did nothing wrong. It was simply blocked on you, and nothing told you. Multiply that by three agents and a good chunk of your afternoon quietly disappears into idle time.
Openbar puts every agent session in the notch, that spot at the top of your screen. It is free and open source, and it runs on Mac, Windows and Linux. The notch is always visible, whatever app you are in, which is exactly why it works as a place for alerts.
The twist
Most tools in this space try to make agents smarter or faster. This one does neither. It makes you faster at answering them.
When an agent asks a question or wants permission, you see the actual command or diff right there in the notch. You answer by typing or by voice, without leaving whatever you were doing. You can also start the next agent with its prompt straight from the notch. So the notch works as both the inbox and the launcher.
That shifts what the bottleneck is. Agents wait on you, so the thing to optimize is your response time. Think about it this way: if an agent takes ten minutes on a task and then waits fifteen minutes for your approval, the slow part was never the model. Cutting that wait from fifteen minutes to fifteen seconds is a bigger win than any speed upgrade on the agent side. And voice makes it even lighter. A quick “yes, go ahead” while your hands are busy in another app beats switching windows, finding the right tab and typing it out.
Mini-workflow
- 🚀 Give each agent its own separate task (Claude Code, Codex, Gemini CLI, whichever fits). Write each prompt so the agent has everything it needs, which means fewer questions later
- 👀 Keep working on your own stuff while they run. The point is to stay in your own flow, not to hover over the notch
- 🔔 When one needs you, check the command or diff in the notch. Read what it actually wants to run before you decide
- 🎙️ Approve or answer by typing or by voice. Short answers are fine, but be specific if the agent asked an open question
- Start the next agent with its prompt from the same place, so the notch stays your single control point
Pro tips
- Keep the tasks truly separate. One commenter on the original post pointed out that context switching is the annoying part with these agents. They also said they would watch how noisy it gets with three of them asking things at once. That is a fair concern. If your agents touch the same files, you will get more interruptions, not fewer. A simple way to split work is by folder or by layer: one agent on tests, one on docs, one on a single feature branch.
- Start with two agents, not five. See how the prompts feel, then add more once you trust your own answering rhythm. Two agents is enough to learn how often each one tends to stop and ask.
- Read the diff before you approve it. A fast approval flow is only a win if you are still actually reading what you approve. If you catch yourself tapping yes without looking, slow down for a day.
- Front-load the instructions. Most of the questions agents ask come from missing context. If you tell each agent which files are off limits and which commands are fine to run, you will get fewer prompts in the notch and the ones you get will matter more.
- Use voice for the easy calls and typing for the careful ones. A yes on a harmless read command can be spoken. A change to a config file or a delete deserves your eyes and a typed reply.
Call to action
If you juggle more than one coding agent, grab it and try it on a real afternoon of work. It is free, so the only cost is a few minutes of setup: https://github.com/MF-DEEV/Openbar
Then tell me whether the notch gets noisy or stays calm. I want to know what happens at three agents. ⚓
My workflow for running several coding agents in parallel without missing their prompts
by u/Significant-Sea-7238 in PromptEngineering