Meet Copilot Buddy — a tiny desk companion that gives your AI coding assistant a body and a heartbeat. It comes alive as you work: cheering you on, lighting up when it needs you, and napping when things are calm. Best of all, you stay in charge — a single press lets you approve or stop your assistant on the spot, no eyes glued to the screen. It levels up, throws confetti for your wins, and keeps you company all day. Part loyal sidekick, part desk pet you'll actually love.
No reviews yetBe the first to leave a review for Copilot Buddy
Maker
📌
Hey hunters 👋
So here's the thing. I code with AI assistants all day, and I kept running into the same goofy problem. My assistant would sprint ahead like a caffeinated intern, then screech to a halt waiting for me to say "yep, go for it." Meanwhile I'm across the room making coffee, leaving the poor thing hanging. Or it'd quietly finish something amazing and I wouldn't notice for ten whole minutes. I was basically babysitting a screen all day. Not the dream.
So I thought: what if I yanked that moment off my screen and plopped it right onto my desk? And that's how Copilot Buddy was born. A tiny little companion that sits by your keyboard, shows you what your AI is up to, and gives you a happy chirp or a blink the second it needs you. Tap to approve. Tap to stop. You're the boss, no screen-staring required.
Real talk: it started as a total weekend goof. A desk pet, just for fun. But the more I lived with it, the more that little approve-or-stop button became the actual magic. And the personality? Completely won me over. So the goof grew up. Now it has moods, it levels up while you work, it naps when things get quiet, and yes, it throws a tiny confetti party every time you ship. 🎉
This one is a genuine labor of love from our pint-sized team at Loopdesk. Totally independent, not affiliated with GitHub or Microsoft, just made by someone who wanted coding with AI to feel a little more alive and a lot more fun.
Tell me what you think, and what your buddy should learn to do next. 🐣
Report
The core problem you're solving is real - agent workflows have a broken approval loop. You're expected to sit and watch for the 'can I proceed?' prompt, which defeats the whole point of delegating to an agent. A physical interrupt button that works while you're away from the screen is a legitimate answer.
My skepticism is on the desk pet framing. "Throws confetti for your wins" and the cheerleading layer feel like things that get turned off within the first week. The control mechanism is the durable value here - the personality risks being the thing that keeps developers from putting it on their desk at all. Is there a minimal mode for people who want the button without the buddy?
Report
Maker
@galdayan yes, as a solo maker I do plan to launch a minimal mode (4th mode) which will arrive as a firmware update next week.
Currently it has 3 modes,
1) Display-only
mirrors your active Copilot CLI session on the device, so you always see what it is doing. No approvals, nothing to configure.
2) Hardware approvals
Pair your device once, then approve or deny Copilot's actions with a button. Always optional, and it falls back to your terminal if the device is not around.
The core problem you're solving is real - agent workflows have a broken approval loop. You're expected to sit and watch for the 'can I proceed?' prompt, which defeats the whole point of delegating to an agent. A physical interrupt button that works while you're away from the screen is a legitimate answer.
My skepticism is on the desk pet framing. "Throws confetti for your wins" and the cheerleading layer feel like things that get turned off within the first week. The control mechanism is the durable value here - the personality risks being the thing that keeps developers from putting it on their desk at all. Is there a minimal mode for people who want the button without the buddy?
@galdayan yes, as a solo maker I do plan to launch a minimal mode (4th mode) which will arrive as a firmware update next week.
Currently it has 3 modes,
1) Display-only
mirrors your active Copilot CLI session on the device, so you always see what it is doing. No approvals, nothing to configure.
2) Hardware approvals
Pair your device once, then approve or deny Copilot's actions with a button. Always optional, and it falls back to your terminal if the device is not around.
3) Demo Mode - Plays all the features in a loop
https://www.instagram.com/p/DaFhhmHvgip/
Thank you for your feedback.