Your AI agent already has a brain. Minnie gives it a body — a floating 3D pet for your Mac that does real work by driving the agent you already use: Claude Code, Gemini, Codex, or any CLI. Before anything risky runs, a cartoon speech cloud shows the exact command — deny or allow, by voice or click. Her 8 moods mirror the agent live. She talks, listens, and remembers. No telemetry, secrets in Keychain, zero extra AI cost.
No reviews yetBe the first to leave a review for Minnie
Maker
📌
Hey PH — Pratik here, solo dev from India.
I built Minnie because of one specific moment: I told Claude Code to "just fix it" on my own laptop, walked away for chai, and came back to a terminal full of commands I had never read. Nothing broke that day. But I realized I'd stopped supervising the thing that has shell access to my machine — because supervising a wall of scrolling text is miserable.
Yes, the CLI already prompts for permission — but a prompt buried in a terminal you alt-tabbed away from isn't supervision. Minnie puts the question on your screen: a speech cloud with the exact command, verbatim, answered out loud — deny, allow once, or allow for the session. That consent cloud started as a safety feature and became the reason I actually let my agent run autonomously.
My design rule: Clippy died because it interrupted you; Tamagotchis died because they did nothing. Minnie only earns a mood when something real happens.
Honest limitations: this is v1 — she's a pet; occasionally she behaves like one. macOS only (Apple Silicon). You need an agent CLI installed and logged in — Claude Code gets the deepest integration; Gemini, Codex, and custom CLIs work too. Built and supported by one person: bugs get fixed fast, but by that same one person.
Everything stays local: no telemetry, no screen capture, on-device voice by default, secrets in Keychain. $19 one-time for the first 500, then $39.
One question: there's a toggle to auto-allow read-only actions while everything else asks. Should that be on by default, or should v1 ask about literally everything? Your answer sets the default.
Report
Love the body for the agent idea, and the speech cloud approve/deny is a really thoughtful safety layer. One thing I'd love: let Minnie pipe allowed commands through a quick dry-run preview on long-running scripts, showing the diff of files she'll touch before I tap allow. Would save me from that "uh, what did I just approve" feeling.
Report
Maker
@nazls86733 Thank you — that "uh, what did I just approve" feeling is exactly the enemy Minnie exists to kill.
Honest take on your idea: for file edits, very doable — the agent already streams structured edit previews, so showing the diff inside the consent cloud before you tap Allow is a natural upgrade. It's going on the roadmap today.
For arbitrary shell scripts, a true dry-run is trickier (running the script is the side effect), but I'm exploring a middle ground: surfacing the paths a command will touch when derivable — and the activity timeline already logs every step after the fact.
Quick question back: would diff-on-edits cover most of your "what did I approve" moments, or is it the shell scripts that bite you?
The speech cloud showing the exact command before it runs is genuinely clever — finally a way to let an agent loose without white-knuckling it. She also feels surprisingly alive on the desktop, not just a gimmick.
Report
Maker
@helindiyar5o3i This genuinely made my day — "without white-knuckling it" is exactly the feeling I built the cloud for. It started as a safety feature and became the thing that made me finally trust my own agent to just run. Glad it lands the same way for you.
And thank you for the "not a gimmick" — that was the hardest line to walk. The rule I held to: she only reacts when something real happens (her moods are the agent's live state, not random cuteness). If you want it the day it ships: https://pratik-singh-web.github.io/minnie-landing/ 🐾
Report
honestly the speech cloud approval thing is such a smart idea, no more doomscrolling through logs to catch what the agent is about to do
Report
Maker
@talha6u9u Right?? Logs are past-tense — you read what already happened. The cloud is present-tense: it comes to you, before the command runs, and waits. And it shows the command verbatim, never a friendly "tidying up some files" summary — that paraphrase is exactly where trust leaks. Really appreciate you getting it. 🐾 If you want it the day it ships: https://pratik-singh-web.github.io/minnie-landing/ 🐾
Love the body for the agent idea, and the speech cloud approve/deny is a really thoughtful safety layer. One thing I'd love: let Minnie pipe allowed commands through a quick dry-run preview on long-running scripts, showing the diff of files she'll touch before I tap allow. Would save me from that "uh, what did I just approve" feeling.
@nazls86733 Thank you — that "uh, what did I just approve" feeling is exactly the enemy Minnie exists to kill.
Honest take on your idea: for file edits, very doable — the agent already streams structured edit previews, so showing the diff inside the consent cloud before you tap Allow is a natural upgrade. It's going on the roadmap today.
For arbitrary shell scripts, a true dry-run is trickier (running the script is the side effect), but I'm exploring a middle ground: surfacing the paths a command will touch when derivable — and the activity timeline already logs every step after the fact.
Quick question back: would diff-on-edits cover most of your "what did I approve" moments, or is it the shell scripts that bite you?
And if you want to kick the tires when it ships — join the waitlist here: https://pratik-singh-web.github.io/minnie-landing/ (30-second form, locks in the $19 founder price). 🐾
The speech cloud showing the exact command before it runs is genuinely clever — finally a way to let an agent loose without white-knuckling it. She also feels surprisingly alive on the desktop, not just a gimmick.
@helindiyar5o3i This genuinely made my day — "without white-knuckling it" is exactly the feeling I built the cloud for. It started as a safety feature and became the thing that made me finally trust my own agent to just run. Glad it lands the same way for you.
And thank you for the "not a gimmick" — that was the hardest line to walk. The rule I held to: she only reacts when something real happens (her moods are the agent's live state, not random cuteness).
If you want it the day it ships: https://pratik-singh-web.github.io/minnie-landing/ 🐾
honestly the speech cloud approval thing is such a smart idea, no more doomscrolling through logs to catch what the agent is about to do
@talha6u9u Right?? Logs are past-tense — you read what already happened. The cloud is present-tense: it comes to you, before the command runs, and waits. And it shows the command verbatim, never a friendly "tidying up some files" summary — that paraphrase is exactly where trust leaks. Really appreciate you getting it. 🐾
If you want it the day it ships: https://pratik-singh-web.github.io/minnie-landing/ 🐾