Auggie,
in your notch.

Augment’s Auggie CLI notifications on your Mac

Gnista shows every Auggie session in your MacBook’s notch: working or done, the session’s title, your prompt, the tool it’s on and its reply. One click takes you to its tab.

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

Gnista with Auggie, at a glance.

Where it runs
Augment’s CLI (auggie) in any terminal.
Setup
Hooks in ~/.augment/settings.json, after a backup.
Needs you
No: Auggie’s Notification hook never fires, so Gnista can’t tell when it waits.
Answer from the notch
No: Auggie’s hooks can deny a tool but not allow one.
Reply from the notch
Yes, typed into its terminal: Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.
In the row
The session’s title, your latest prompt, the tool it’s running and its reply, and with Auggie 1.x a badge for the model.
Subagents
Shown on the row of the session that started them, as delegating; no row of their own.
Cost and limits
With Auggie 1.x, context and cost at the model’s list price; none with 0.36, and no plan limits.

What it’s doing, without the tab.

Rows read Auggie’s own session record, in ~/.augment/sessions-v2/ from 1.x or ~/.augment/sessions/ before: the title, your latest prompt, the tool it’s running, the file it reads or edits, and its reply when the turn ends.

Subagents, on one row.

When Auggie hands work to a subagent, the row of the session that started it says so. The subagent gets no row of its own, so your list stays one line per session.

One click to the tab.

Click the row and Gnista brings up the terminal tab Auggie runs in, ready for your answer.

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

  • “Needs you”: Auggie’s Notification hook never fires, so a request waiting in Auggie shows as working.
  • Answering from the notch: Auggie’s hooks can deny a tool, but its allow is dropped, so you answer in Auggie.
  • Cost and context come only from Auggie 1.x, whose session files count tokens; 0.36’s record has none. Augment bills in credits, so the cost is the model’s list price, not your bill.
  • Replies from the notch are typed into its terminal, so they need Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.
02Setup

Connected in a minute.

  1. Open Gnista and tick Auggie.
  2. Gnista backs up ~/.augment/settings.json and adds its hooks, keeping yours.
  3. Start a new auggie session.
03FAQ

Auggie, asked and answered.

Can I approve Auggie from the notch?

No. Auggie drops a hook’s allow and only honours a deny, so answer in Auggie.

Why doesn’t Gnista show when Auggie needs me?

Auggie’s Notification hook never fires, so Gnista shows working and done, and what Auggie is doing.

Can I reply to Auggie from the notch?

Yes, in Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension: Gnista types your reply into the session’s terminal.

Does it show what Auggie costs?

With Auggie 1.x, yes: its session files count tokens, which Gnista prices at the model’s list price, as Augment itself bills in credits. Auggie 0.36’s record has no tokens, so no cost.

How do I remove it?

Settings ▸ Agents ▸ Auggie ▸ Disconnect. Exactly Gnista’s hooks go; yours stay.

Gnista also keeps an eye on

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