When you run several Claude Code sessions side by side, one of them is often stuck in a background tab asking “May I write this file?”, and you don’t notice for a long time.
So I had Codex (OpenAI’s coding agent) build a Windows app: a desktop pet that tells you when Claude Code is waiting for approval, and clicking its speech bubble takes you straight to the tab that is waiting. It works for Windows Terminal tabs and for VS Code’s integrated terminal.
Short answer: download the ZIP and double-click the exe. Nothing to configure in Claude Code (no hooks). Only if you want to jump to VS Code integrated terminal tabs do you install a tiny bundled VS Code extension (VSIX) once.

Note: the pet’s chatter and labels are in Japanese (it was made for my own use). The approval notice works the same regardless, and the source is included if you want to translate the lines.
The pets and what they do
There are two characters: Orange-chan, a network engineer, and ACK, a four-armed network maintenance robot. Both were drawn by Codex with image generation and are original designs. You can switch between them at any time with the buttons below the pet.

| Action / situation | Orange-chan | ACK |
|---|---|---|
| Click | Tells a bit of networking trivia (12 stories, sometimes mutters while troubleshooting) | Gives an “acknowledged” signal |
| Double-click / long press | Types at a desk | Works on a server rack |
| Drag left/right | Runs in that direction (carrying a cable). Press Esc while dragging to put it back | |
| Idle for 60 seconds | Takes a break with a phone plus an iced coffee | Goes into power-saving mode |
| Claude Code waiting for approval | Shows “承認待ち” with the session name above it, pointing at it. Click to jump to the tab | |
| Buttons below | “−” / “+” resize from 50% to 100%, “ACK” / “戻す” switch character, “隠す” / “表示” hide or show | |
| Right-click | Pick an animation, set a size, quit | |


From the notice to the waiting tab
Windows Terminal
Here Claude Code is running in one tab while I work in another (PowerShell) tab. The waiting tab isn’t visible, but the pet’s bubble says “承認待ち メモファイル作成テスト” (waiting for approval: note file test).

Click the bubble. I had two Windows Terminal windows open, so a menu asked which window to use (with only one window it jumps straight there).

After choosing, it switched to the waiting “メモファイル作成テスト” tab. Now just answer Yes or No there.

VS Code integrated terminal
Here Claude Code runs in VS Code’s integrated terminal, and then I opened another terminal (pwsh) in front of it. The waiting tab is listed on the right but not shown.

Click the bubble and VS Code asks whether to allow the extension “デスクトップペット 端末タブ切替” (desktop pet terminal tab switcher) to open this URI. This is VS Code’s standard confirmation for the helper extension (VSIX) explained below. Press Open. If you don’t want to be asked every time, tick “Don’t ask again for this extension”.

It switched to the waiting terminal tab showing “Do you want to create note.txt?”.

If you use the Claude Code VS Code extension (the sidebar / editor tab version) instead, the pet can open that conversation without the VSIX, because the extension officially provides a URI that opens a session (see “How it works”).
Download and setup
The ZIP contains two exe files, the VS Code helper extension, a readme and the full source.
desktop-pet-orange-ack.zip (about 6.7MB)
| File | What it is |
|---|---|
オレンジちゃん.exe |
Starts with Orange-chan. The images are embedded in the exe |
ACK.exe |
Starts with ACK (same program, different starting character) |
DesktopPetTerminalFocus.vsix |
Helper extension for jumping to VS Code integrated terminal tabs. Optional |
はじめに.txt |
Readme (Japanese) |
source\ |
Source code, images and the build script |
Requirements: Windows 10/11 with .NET Framework 4.8 or later (preinstalled on Windows). The pet itself needs neither Claude Code nor an internet connection.
1. Unblock and extract the ZIP
Right-click the downloaded ZIP, choose Properties, tick “Unblock” under Security at the bottom and press OK. Then right-click and choose “Extract All”. Don’t run the exe from inside the ZIP (its settings can’t be saved there).
To check that the ZIP isn’t corrupted, compare its hash in PowerShell with the value below.
Get-FileHash .\desktop-pet-orange-ack.zip -Algorithm SHA256
91CD2A08F3F33A8D7BB78E16AEABC132E70892DFCF050D27BF2427047621FEA7
2. Double-click the exe
Double-click オレンジちゃん.exe and the pet appears at the bottom right of the screen. If “Windows protected your PC” (SmartScreen) appears, click “More info” and then “Run anyway”. It shows up because this is an unsigned exe made by an individual. If that bothers you, build the exe yourself from the source as described below.
To quit, right-click the pet and choose “終了” (Quit). Size and character are saved in a .settings file next to the exe and restored next time. It doesn’t start with Windows; launch it when you need it.
3. (Optional) Install the VS Code helper extension
Only needed if you run Claude Code in VS Code’s integrated terminal and want to jump to that tab. Not needed for Windows Terminal or the Claude Code extension.
In VS Code open Extensions, click “…” at the top, choose “Install from VSIX…” and pick DesktopPetTerminalFocus.vsix. From PowerShell, run this in the extracted folder:
code --install-extension .\DesktopPetTerminalFocus.vsix
On a work PC, follow your company’s rules for installing extensions.
How it works
Detecting “waiting for approval”
Claude Code has hooks that can run a command when it waits for approval, but I wanted the pet to work on my work PC too, where hooks are disabled by policy. So it reads the state files Claude Code writes on its own, which means there is nothing to configure in Claude Code.
For every running session, Claude Code keeps a “PID.json” file in .claude\sessions\ under your user folder. About every 2 seconds the pet reads all of them and shows a bubble only when the following conditions hold. The session name comes from the conversation log under .claude\projects\.
| Field | What it checks |
|---|---|
status |
Is it waiting? |
waitingFor |
Is it a permission prompt? Normal input waits are ignored |
pid and start time |
Is that process still running with the same start time? This skips stale files and reused PIDs |
sessionId |
The session ID, used to find the name and to open the session in VS Code |
cwd |
Working folder, used to pick the VS Code window |
entrypoint |
CLI or the Claude Code VS Code extension |
The contents of these files are not a documented specification, so an update may break the notices (confirmed working with Claude Code 2.1.330 on November 22, 2026).
Finding the window and tab
When you click the bubble, the pet walks up the parent processes of the waiting Claude Code process until it reaches WindowsTerminal or Code (VS Code); that is the window to bring forward. For VS Code it narrows windows down by folder name and window title, and shows a menu if it can’t decide. The tab is chosen like this:
| Target | How the tab is selected | VSIX |
|---|---|---|
| Windows Terminal | Uses Windows UI Automation (the API for driving UI elements from outside) to list the tabs and selects the one whose name matches the session name, ignoring symbols such as “✳” that Claude Code puts in front | Not needed |
| Claude Code VS Code extension | Passes the extension’s official session URI (vscode://anthropic.claude-code/open?session=SESSION_ID) to VS Code |
Not needed |
| VS Code integrated terminal | Passes the helper extension’s URI (vscode://local-pets.desktop-pet-terminal-focus/focus?pids=LIST_OF_PIDS) to VS Code |
Required |
The VSIX that selects the integrated terminal tab
Integrated terminal tabs can’t be told apart from outside, but an extension inside VS Code knows each tab’s shell PID. So the pet sends the list of PIDs it walked through as a vscode:// URI, and the extension shows the matching tab. This is the whole extension (source\TerminalFocus\extension.js):
const vscode = require('vscode');
function activate(context) {
context.subscriptions.push(vscode.window.registerUriHandler({
async handleUri(uri) {
if (uri.path !== '/focus' || vscode.env.remoteName) return;
const ids = new URLSearchParams(uri.query).get('pids') || '';
if (!/^\d+(,\d+){0,31}$/.test(ids)) return;
const ancestors = ids.split(',').map(Number);
const matches = [];
for (const terminal of vscode.window.terminals) {
const pid = await terminal.processId;
const rank = ancestors.indexOf(pid);
if (rank >= 0) matches.push({ terminal, rank });
}
matches.sort((a, b) => a.rank - b.rank);
if (matches.length && (!matches[1] || matches[0].rank !== matches[1].rank)) {
matches[0].terminal.show(false);
} else {
vscode.window.showInformationMessage('承認元の端末をこのウィンドウで特定できませんでした。');
}
}
}));
}
module.exports = { activate };
Anything in pids= other than digits and commas (max 32 entries) is discarded, and it does nothing in remote VS Code windows. It never presses approval buttons and makes no network calls. Its package.json is below; it only activates when the URI arrives.
{
"name": "desktop-pet-terminal-focus",
"displayName": "デスクトップペット 端末タブ切替",
"description": "承認通知から、指定したシェルPIDのローカル端末を表示します。",
"publisher": "local-pets",
"version": "1.0.0",
"engines": { "vscode": "^1.85.0" },
"extensionKind": ["ui"],
"activationEvents": ["onUri"],
"main": "./extension.js"
}
What to change: quick reference
Everything is in source\: three C# files and two images, small enough to play with lines and artwork. Feel free to modify, use and redistribute the source and images (no need to ask, no warranty).
| What you want to change | File / line | How |
|---|---|---|
| Character name | CharacterPet.cs line 13 |
The PetName string |
| Lines spoken on click (12 stories) | CharacterPet.cs lines 16-27 |
4 lines per story (about 2 seconds each). Add lines for more stories. This is where you translate them |
| Troubleshooting mutterings (8 stories) | CharacterPet.cs lines 30-37 |
Also 4 lines per story |
| How long speech stays | CharacterPet.cs line 384 |
8 seconds in return 8; |
| Time before the break animation | CharacterPet.cs line 415 |
60 seconds in >= 60 |
| Animation speed | CharacterPet.cs line 68 |
Frame time per animation (ms) |
| Start position | CharacterPet.cs lines 123-124 |
24 px from the right edge, 16 px from the bottom |
| Color of the approval bubble | CharacterPet.cs line 134 |
Replace Brushes.DarkOrange |
| Polling interval | CharacterPet.cs line 195 |
2 seconds in FromSeconds(2) |
| Orange-chan artwork | Orange-atlas.png |
Transparent PNG, 192×208 px per frame, 3 frames × 8 rows (greet, run right, run left, talk, type, break, troubleshoot, waiting) |
| ACK artwork | ACK-atlas.png |
192×208 px per frame, 4 × 5 grid, 10 animations of 2 frames |
| Min / max size | PetDisplay.cs line 84 |
.5 (50%) and 1 (100%) |
After editing, open PowerShell in the source folder and run the command below. It uses the C# compiler that ships with Windows (csc.exe), so you don’t need Visual Studio. The exe files and the VSIX are written to source\out\.
powershell -ExecutionPolicy Bypass -File .\build-blog.ps1
Quit any running pet first, or the exe can’t be overwritten. I confirmed the build works in both Windows PowerShell 5.1 and PowerShell 7.
Limitations
- You can’t approve (Yes/No) from the pet. It takes you to the tab and you answer there
- The state files are undocumented, so a Claude Code update may stop the notices
- If you renamed a Windows Terminal tab by hand, or several tabs share a name, it can only bring the window forward
- Split panes in Windows Terminal, and Claude Code running inside WSL or over SSH, are not supported
- If the same folder name is open in several VS Code windows, or your window title doesn’t include the folder name, a menu asks which window
- Only Claude Code running as the same Windows user is detected. If you set
CLAUDE_CONFIG_DIR, start the pet with the same value - I have only tested it on my own PC
How I built it with Codex
I started with “make a desktop pet that uses neither ChatGPT nor the network”, then added requests while using it: “tell me when Claude Code waits for approval”, “take me back to that tab”, “I want a robot too”. It reached its current form in about two days. Each time, Codex triggered a real approval prompt to test it. Only the VS Code window matching was later fixed by Claude Code.
Summary
- Extract the ZIP and double-click the exe. Nothing to configure in Claude Code
- A bubble appears when approval is needed, and a click takes you to that tab
- Source and images are free to modify; rebuild with
build-blog.ps1
References
- Hooks reference - Claude Code Docs (Notification hook and
permission_prompt) - Explore the .claude directory - Claude Code Docs (one file per running session in
sessions/) - Use Claude Code in VS Code - Claude Code Docs (
sessioninvscode://anthropic.claude-code/open) - VS Code API - Visual Studio Code (
window.registerUriHandler,Terminal.processId,Terminal.show) - Activation Events - Visual Studio Code (
onUri) - UI Automation Overview - Microsoft Learn
Tested on: Windows 11, Windows Terminal, VS Code, Claude Code 2.1.330 (CLI), .NET Framework 4.8. Checked on November 22, 2026.


コメント