CodeBuddy,
in your notch.

CodeBuddy Code notifications and approvals on your Mac

Gnista shows every CodeBuddy Code session in your MacBook’s notch: working, done, or waiting for you. When it wants to run something, allow or deny it there. When a turn is done, reply there.

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

Gnista with CodeBuddy, at a glance.

Where it runs
CodeBuddy Code’s interactive CLI, in any terminal.
Setup
Gnista adds its hooks to ~/.codebuddy/settings.json, after a backup; CodeBuddy asks you to trust each folder once.
Needs you
Permission requests, the moment they happen, with the command it wants to run, and its questions.
Answer from the notch
Allow or Deny, and answers to its questions; there’s no Always.
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 prompt, the latest reply, the tool it’s running, and task progress.
Subagents
Shown in the row while they work, with each one’s task and step, and how many are done.
Cost and limits
The credits the session used, and once Settings ▸ General ▸ Usage isn’t Off, the context ring, through CodeBuddy’s status line; no dollar price or plan limits.

Allow. Deny. Keep going.

When CodeBuddy Code wants permission, the notch opens with the command it wants to run. Allow it and it runs; deny it and CodeBuddy shows “Denied from Gnista” and carries on without it.

The tool, not the wrapper.

CodeBuddy runs its tools from small pieces of code. Gnista reads past them, so the row says the command or file CodeBuddy is working on, not just “REPL”.

Its own record, read for you.

Gnista reads CodeBuddy’s session file for the title, your prompt, its reply, task progress, the subagents at work and the credits the session used.

One more thing? Reply.

When a turn is done, type a reply in the notch and Gnista types it into CodeBuddy’s terminal: Terminal, iTerm, Ghostty, a tmux pane, or an editor’s terminal with Gnista’s extension.

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

  • No Always: CodeBuddy doesn’t take rules from a hook, so Gnista answers one request at a time, with Allow or Deny, or your answers to its questions.
  • Print mode (codebuddy -p) refuses permissions before any hook runs, so there’s nothing for Gnista to answer there.
  • No dollar price or plan limits: CodeBuddy bills in credits, so the row shows the credits a session used. The context ring comes only through CodeBuddy’s status line.
  • Replies are typed into the session’s terminal, so they work in 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 CodeBuddy.
  2. Gnista backs up ~/.codebuddy/settings.json and adds its hooks, keeping yours.
  3. Start CodeBuddy in your project. The first time in a folder, it asks you to trust it; say yes.
03FAQ

CodeBuddy, asked and answered.

Can I approve CodeBuddy from the notch?

Yes, in its interactive CLI: Allow runs the command, Deny stops it, and its questions take your answers. There’s no Always.

Can I approve codebuddy -p runs from the notch?

No. In print mode CodeBuddy refuses permissions itself, before any hook runs, so there’s nothing to answer.

Why credits and not a price?

CodeBuddy bills in credits and doesn’t say which model it used, so Gnista shows the credits each session used, as CodeBuddy counts them.

Is this Tencent’s CodeBuddy?

Yes: CodeBuddy Code, its agent for the terminal.

How do I remove it?

Settings ▸ Agents ▸ CodeBuddy ▸ 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.