Goose,
in your notch.

Goose notifications, replies and cost on your Mac

Gnista shows every Goose session in your MacBook’s notch: working or done, the tool it’s on, its reply when the turn ends, and what the session cost. One click takes you to its tab.

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

Gnista with Goose, at a glance.

Where it runs
The Goose CLI (goose) in any terminal.
Setup
A plugin of Gnista’s own in ~/.agents/plugins/gnista/, which Goose turns on itself.
Needs you
No: Goose asks in its own prompt before any hook runs.
Answer from the notch
No: its hooks can’t see or answer its prompt.
Reply from the notch
Typed into its terminal: Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.
In the row
The command it runs or the file it edits, and its reply when the turn ends.
Subagents
No: Goose’s hooks don’t report them.
Cost and limits
Tokens, context and cost, read from Goose’s own sessions database: its provider’s cost where it has one, else the model’s list price.

A plugin, not a patch.

Goose finds every plugin folder in ~/.agents/plugins/ and turns it on by itself. Gnista’s is a folder of its own, with its hooks in Claude’s format, so nothing of yours is edited, and Disconnect removes just that folder’s hooks.

What it costs, as it goes.

Goose adds each reply’s tokens and cost to its sessions database. Gnista reads them, so the row shows how full the context is and what the session cost. For a model Gnista doesn’t know, describe it in a model file.

One more thing? Reply.

When a turn is done, type a reply in the notch, and Gnista types it into Goose’s terminal, without switching you there.

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

  • “Needs you”: Goose asks before a tool in its own prompt, before any hook runs, so a waiting Goose shows as working.
  • Answering from the notch: for the same reason, you answer in Goose.
  • Replies from the notch are typed into its terminal, so only in Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.
  • Goose reads its hooks when a session starts, so a session already open reports only once you start a new one.
02Setup

Connected in a minute.

  1. Open Gnista and tick Goose.
  2. Gnista adds a plugin of its own, ~/.agents/plugins/gnista/, with its hooks in hooks/hooks.json. Goose finds it and turns it on by itself; your Goose config stays as it is.
  3. Start a new Goose session.
03FAQ

Goose, asked and answered.

Why doesn’t Gnista show when Goose needs me?

Goose asks before a tool in its own prompt, before any hook runs, so no hook hears it. Gnista shows working and done, and what Goose is doing.

Does it change my Goose config?

No. Gnista’s hooks live in a plugin folder of its own, ~/.agents/plugins/gnista/, which Goose turns on by itself.

And without the plugin?

Gnista still sees Goose working by its process, with Settings ▸ Agents ▸ Detect agents without hooks on, but with no tool, reply or cost.

How do I remove it?

Settings ▸ Agents ▸ Goose ▸ Disconnect. Exactly Gnista’s hooks go.

Gnista also keeps an eye on

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