Coding agents ask the same few questions all day: which branch? full test suite or just the changed files?
Clippy's standing orders answer the routine ones ("whenever an agent asks which branch, say staging"). Anything an order doesn't clearly cover still comes to me.
Back from lunch with a few agents running? Hit Ctrl+Alt+Space and ask Clippy "what happened while I was at lunch?"
He summarises what your agents left for you and what's still waiting on you. 🥪
github.com/geetbatth/profess…
Agents are great at writing checklists and terrible at putting them somewhere you'll actually see them.
So Clippy has a Pad: an agent can leave you a page (a checklist, a summary), and you can pin any page to the desktop as its own little sticky. 📌
My take on the "is it vibe coding?" debate: it stops being vibes when there are tests.
Clippy is 71 of 72 commits co-authored by Claude Code, but every feature went spec → plan → tests first. It has about 1,100 tests now.
Small MCP tip: give your agents a tool that blocks.
Clippy's ask_user holds the agent's tool call until a human answers, with the options shown as buttons. No polling, no "check back later", and I can answer from my phone.
github.com/geetbatth/profess…
Happy Halloween 🎃
Scariest thing on a dev's screen: a coding agent that's been sitting on a yes/no question for an hour while you were out.
Clippy sends those to WhatsApp or Telegram when you're away, and your answer goes straight back to the agent.
Agents keep getting smarter, but how they reach us is still "go check the terminal".
I gave mine a sticky note. Questions pop up with answer buttons, permission prompts come through, and "I'm done" waits quietly unless I've walked away.
How do yours ping you?
Run a few Claude Code sessions at once and you become a foreman checking terminals every five minutes.
So my agents ask through a desktop sticky note: ask_user blocks until I tap an answer, even from my phone.
github.com/geetbatth/profess…
Halloween costume idea: the paperclip that interrupted everyone's letters in 1997.
I went the other way and built a Clippy who's quiet by default. He only pops up when one of my AI agents actually needs me. Everything else waits under an unread badge. 📎🎃
Meet Professor Clippy 📎🎓
He's a sticky note for your Windows desktop with a little robot professor standing on it. Your AI agents (Claude Code, or any MCP client) leave him notes, reminders and questions. He pops up, wiggles, and waits until you deal with them.
Coming next: email 📬
Those "we sent you a verification code" emails? Clippy grabs the code and pops it up with a Copy button, so you never have to open your inbox.
He'll also flag the emails that actually matter. Read-only Gmail, runs on your PC.
It looks like you're trying to get things done. Would you like help? 📎
github.com/geetbatth/profess…
All @LDoerkson has to do is take out all the bs rules that make reno and flip unprofitable. That's it and BC economy will pump again 100%
so there are two ways to prompt ai
1. you give it a lot of information tell it to do exactly as you say
2. you give it as little info as possible
you want to lean towards 2 more than 1 . if you do 1 too much it will slow you down.