Claude Code New

When Claude Code needs your permission, has a question or is done, Poni shows it under the closed notch, and you can answer right there without going back to the terminal. For Claude Code on this PC: in a terminal, in VS Code or in the Claude app.

Settings → Claude Code

Setting it up

It's off from the start, and it takes two things: the switch, so Poni listens, and Poni's hooks in Claude Code's settings, so Claude Code tells Poni.

Open Settings → Claude Code and turn on Show Claude Code’s requests.
Click Install. The line next to it changes to Connected to Claude Code.
A Claude Code session that was already running may need a restart to use the hooks. New sessions use them straight away.
The next time Claude asks for permission, the card shows under the closed Poni.

Option	What it does
Show Claude Code’s requests	Poni listens for Claude Code and shows its cards. Default: off.
Answer permissions from Poni	Allow, Deny or pick an answer right in Poni. Off: the card only tells you, and Claude Code asks in its own window straight away. Default: on.
Tell me when Claude is done	A card with the start of Claude's last message and a soft sound when it finishes. Default: on.
Install / Remove	Puts Poni's hooks into Claude Code's settings file, or takes them out. See below.

The cards

Each card says what Claude wants, with the project at the right: the name of the folder Claude Code started in. A soft sound plays when a card comes (none during Do not disturb). If Poni is open at that moment, its top bar shows Claude needs permission · my-shop for a moment, and the card shows once Poni closes.

Card	What it shows, and the buttons
Claude needs permission	The tool, like Bash, Edit or WebFetch, and what it would do: the command, the file or the address. Allow lets Claude go ahead. Deny stops it, and Claude is told you said no in Poni. Open answers nothing here (see below).
Claude has a question	Claude's question with its answers as chips. Point at a chip to see its description, and click one to answer. When Claude asks several questions (up to four), they come one at a time, marked like 1/2. When more than one answer may be picked, click each one you want, then Next or, on the last question, Send. Open to answer lets you answer in Claude's own window instead.
Claude is done	The start of Claude's last message. Open brings its window forward, Close removes the card.

Open lets Claude Code ask in its own window at once, and Poni brings that window forward: Windows Terminal, VS Code, Cursor, the Claude app, a JetBrains IDE or a console window. If Poni can't find the window, Claude Code still asks there; you only have to switch to it yourself.

While Claude waits for you, its own window says Waiting for your answer in Poni. While a card shows, Poni doesn't open when you point at it and doesn't tuck itself away, so the card stays in sight. Click the top of Poni if you want to open it.

When you don't answer

Claude waits for your click in Poni for up to a minute. Then the card goes, and Claude Code asks in its own window as usual.
When Poni isn't running, or Show Claude Code’s requests is off, Poni's hook steps aside at once and Claude Code asks in its own window, as if Poni weren't there. So you can leave the hooks installed.
With Answer permissions from Poni off, Claude Code asks in its own window right away. The card only tells you, with Open and Close.
A card that only tells you goes when you close it, or by itself after 10 minutes.
When the same session asks something new or is done, its earlier card goes.

Several requests at once

Poni shows one card at a time. The oldest request that waits for an answer comes first, and the cards that only tell you come after those. Under the card, a line says how many more there are and the next one's project, like 1 more waiting · api-server. Answer the card and the next one takes its place.

Install and Remove

Poni changes Claude Code's settings only when you click one of these buttons. The file is %USERPROFILE%\.claude\settings.json (or settings.json in CLAUDE_CONFIG_DIR when you set one).

Install adds three hooks: one for permission requests, one for Claude's questions, and one for when Claude stops. Each runs Poni's poni.exe --claude-hook.
Before it writes, Poni copies the file to settings.json.poni-backup next to it.
Nothing else in the file changes: your other settings and hooks stay, in their order.
Remove takes out only Poni's hooks.

Line in Settings	What it means
Not connected	Poni's hooks aren't there. Click Install.
Connected to Claude Code	All of Poni's hooks are there, for this Poni. If Show Claude Code’s requests is off, the line reminds you to turn it on.
Partly connected	Some of Poni's hooks are missing. Click Install to put them all back.
Connected to a Poni in another folder	The hooks point at another copy of Poni, for example a portable one. Install points them at this one. If the other Poni has been deleted or moved, Poni moves the hooks to itself when it starts.
Claude Code’s settings file has an error	The file isn't valid JSON (Settings says which line), so Poni leaves it alone. Fix it in an editor, then come back.
Claude Code isn’t set up here	Claude Code's settings folder doesn't exist yet. Start Claude Code once, then come back.

Where it works

Claude Code running on this PC, under your Windows account: in a terminal, in VS Code (or another editor) and in the Claude app.
Claude Code sessions that run in the cloud don't run on your PC, so they don't come to Poni.

Read what a permission card says before you click Allow, just as you would in the terminal. Poni passes your answer on; it doesn't check the command.

Privacy

Requests go from Claude Code to Poni through a channel only your Windows account on this PC can open, never over the network, and your answer goes back the same way. Poni's hook only talks to the Poni it belongs to, the same poni.exe.
poni.log notes only the kind of request and the tool's name, never the command or Claude's words.