MiMoCode,
in your notch.

MiMoCode notifications, approvals and replies on your Mac

Gnista shows every MiMoCode session in your MacBook’s notch: working, done, or waiting for you. When MiMo wants to run a command, allow or deny it there, and reply to it once a turn is done.

Try free for 7 days No account, no card · then €19 once
01At a glance

Gnista with MiMoCode, at a glance.

Where it runs
MiMoCode (mimo) in any terminal.
Setup
One plugin file at ~/.config/mimocode/plugins/gnista.js; nothing else changes.
Needs you
Permission requests, with the command, file or folder outside the project, its questions, and its plan once it’s finished.
Answer from the notch
Allow, Always or Deny, answers to its questions, and Approve or Keep planning, sent through Gnista’s plugin inside MiMoCode.
Reply from the notch
Yes, wherever MiMoCode runs: it arrives as your message, with the session’s agent and model kept.
In the row
The title, the agent (plan shows as plan mode), your prompt, the answer, the running tool and the todos.
Subagents
Folded into the row of the session that started them, which shows what they ask.
Cost and limits
Cost and tokens, added up from MiMoCode’s own replies; no plan limits, since MiMoCode keeps none.

Allow. Deny. Keep going.

Gnista’s plugin runs inside MiMoCode, so Allow, Always and Deny go through MiMoCode’s own client, not a keystroke in a terminal. Its own prompt stays up too, and whichever you answer first counts.

Replies that look like you typed them.

When a session is idle, a reply from the notch goes in as a real prompt, with the agent and model the session was using, and shows in MiMoCode as your message. In any terminal.

What it’s doing, and what it costs.

Rows read MiMoCode’s own record: the session’s title, your prompt, its answer, the tool it’s running and its todos. MiMoCode keeps no totals for a session, so Gnista adds up the cost and tokens of each of its replies.

What it can’t do with MiMoCode, and why.

  • No plan limits: MiMoCode doesn’t record any. The row shows its cost instead.
  • Gnista has no model file for MiMo’s own models yet, so the row shows no context bar until you describe the model in one.
  • A MiMoCode that’s already running picks up Gnista only when you restart it.
02Setup

Connected in a minute.

  1. Open Gnista and tick MiMoCode.
  2. Gnista writes one new file, ~/.config/mimocode/plugins/gnista.js, and leaves your MiMoCode config alone, so there’s nothing to back up. If another plugin already has that name, Gnista stops and says so.
  3. To answer from the notch, turn on Answer prompts in Gnista (Settings ▸ General).
  4. Start mimo. One already open picks up the plugin when you restart it.
03FAQ

MiMoCode, asked and answered.

Can I approve MiMoCode from the notch?

Yes: Allow, Always or Deny, its questions and its finished plans, once Answer prompts in Gnista is on (Settings ▸ General).

Why doesn’t Gnista show anything for MiMoCode?

MiMoCode loads plugins when it starts. Restart mimo after connecting.

Can I reply to MiMoCode from the notch?

Yes, once a turn is done. The reply goes in as a real prompt with the session’s agent and model, and shows as your message.

Does it show what MiMoCode costs?

Yes: the cost and tokens of its replies, added up per session.

What does Gnista change, and how do I remove it?

Only its plugin file, ~/.config/mimocode/plugins/gnista.js. Settings ▸ Agents ▸ MiMoCode ▸ Disconnect deletes it; your MiMoCode config is never touched.

Gnista also keeps an eye on

Wrote your own? It can report to Gnista with one line of JSON: custom agents.