Devin,
in your notch.

Devin CLI notifications, approvals and cost on your Mac

Gnista shows the Devin CLI and Devin Local in your MacBook’s notch: working, done, or waiting for you. Allow or deny what Devin wants to run, reply when a turn is done, and jump to its terminal tab or its chat in Devin’s agent panel.

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

Gnista with Devin, at a glance.

Where it runs
The devin CLI in any terminal, and Devin CLI chats in Devin Local’s agent panel.
Setup
Gnista adds its entries to ~/.config/devin/config.json, after a backup; Devin needs the folder trusted once.
Needs you
Permission requests, with the command Devin wants to run.
Answer from the notch
Allow or Deny; there is no Always, and an unanswered request goes back to Devin’s own prompt.
Reply from the notch
Yes, typed into the session’s terminal: Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.
In the row
The title, the mode, your prompt, Devin’s reply, the command it runs and its todos, read from Devin’s sessions.db.
Subagents
Shown in the session’s row: how many are done, and the task of the one still running.
Cost and limits
Tokens and cost at Devin’s own model prices; no plan limits, which Devin doesn’t record.

Allow. Deny. Keep going.

When Devin wants to run something, the notch opens with the command. Allow it, or deny it, and Devin carries on, told that Gnista denied it. If you don’t answer, Devin asks in its own prompt: at once when you’re at its tab, after 10 seconds while the notch is closed, and after 45 seconds at most while you’re in the notch.

Everything Devin knows, in the row.

Gnista reads Devin’s own session database, so the row shows the title, your prompt, the reply, the command, todo progress, subagents, the context used and what the session cost.

Terminal or agent panel, one click.

A Devin CLI session takes you to its tab. A chat in Devin Local’s agent panel opens there, in Devin.

Careful with Devin’s config.

Devin rejects a whole hooks file over one event it doesn’t know, so Gnista writes only the events Devin accepts, in entries of its own. Devin also runs Windsurf- and Cursor-style hooks; Gnista counts each turn once.

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

  • No Always from the notch: a hook can only allow or deny once. For a lasting rule, answer in Devin’s own prompt.
  • Replies from the notch are typed into the session’s terminal, so they work only in Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension. A chat in Devin Local’s agent panel can’t take one.
  • Devin loads hooks when a session starts, so after you connect, sessions already open report only once you reopen them.
  • Cascade, the agent Devin Desktop’s editor had before, isn’t supported: Devin Desktop removed it. Devin Local reports through Devin’s own hooks.
02Setup

Connected in a minute.

  1. Open Gnista and tick Devin.
  2. Gnista backs up ~/.config/devin/config.json to ~/Library/Application Support/Gnista/Backups and adds its own entries, with only the events Devin accepts.
  3. To answer from the notch, turn on Answer prompts in Gnista, in Settings ▸ General.
  4. Start devin in your project. In a folder Devin doesn’t trust yet, it asks once, in the terminal: trust it there, or it won’t run.
03FAQ

Devin, asked and answered.

Can I approve Devin from the notch?

Yes, once Answer prompts in Gnista is on: Allow or Deny. There is no Always. Unanswered, the request goes back to Devin’s own prompt.

Why doesn’t Devin start, or show in Gnista?

Devin won’t run in a folder you haven’t trusted. Start devin there once and trust it in the terminal. A session opened before you connected reports once you reopen it.

Can I reply to Devin 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.

What does a Devin session cost?

The row prices each reply’s tokens at the rates Devin lists for its models. For a model Gnista doesn’t know, describe it in a model file.

Is this the same as Cascade?

No. Cascade was the agent in Devin Desktop’s editor, and Devin Desktop removed it, so Gnista doesn’t support it. Devin Local’s chats report through Devin’s own hooks, as the CLI does.

How do I remove it?

Settings ▸ Agents ▸ Devin ▸ Disconnect. Exactly Gnista’s entries go.

Gnista also keeps an eye on

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