Guarding sessions you start outside AigoPilot

Partly built. The hooks that report to the studio are written and working. The guard that refuses a few irreversible commands is built and was tried in trials, but it is written into Claude Code's settings only when you click for it, and it has not been seen stopping a real incident.

Some sessions are not started by AigoPilot: the ones you run in VS Code or in a terminal. The studio lists them, so you can read what they did and see that they wait for you. This page covers how the studio treats such sessions, how it knows what they are doing, and the optional guard that protects them.

Whose session it is

A session that the studio did not start belongs to the program that did, whether or not that program is open right now. Its row carries a mark such as in VS Code. You can open it and read the whole conversation. The box stays shut, and a band above it says This session belongs to VS Code, not to the studio. It is not continued from here until you bring it into the studio. The studio never takes a session over behind your back.

When you press Bring it into the studio, the studio first checks whether the session is open elsewhere. If its file was written seconds ago, it says so, because continuing one session from two places splits its history in two. If you want another tool to take the work, start a fresh session of it from the old one; nothing is written into the old session.

How the studio knows what it is doing

Claude Code can start a small program whenever a session waits for your permission or your answer, or ends its turn. AigoPilot's program only reports to the studio. It never changes what the session does. With it, a session waiting for permission in VS Code is shown as Waiting for your permission. Without it the studio can only guess from the session's file, and the row reads May be waiting for your permission.

1. Click the gear in the top bar, then News from Claude Code under More. The window Getting news from Claude Code opens.
2. Read which settings file will be written and which program Claude Code will start. Open The file as it will be after writing to see it exactly.
3. Under News, click Write. A copy of the file with the date and time goes beside it first. After writing, the file is read back.
4. Click Test. It says whether the program arrived and how long it took.

The window lists the events it listens for, such as a session asking for permission or a turn ending, and under Latest news the last time each arrived. Hooks you wrote yourself in that file are left alone, and the window says how many there are. Remove takes the studio's entries out again.

The guard

The window has a second part, Guard, with a button of its own. The guard looks at every shell command before it runs and stops three kinds: deleting a folder with all that is in it outside the project, tools for disks and drives, and commands that empty a database. It does not touch ordinary work. It works in every Claude Code session, in the studio or outside it, even when the permission mode is Full access.

The percent of the limit

A third part writes a status line. Claude Code tells how full a limit is only to a program it calls itself. With the status line, every Claude session hands the same number to the studio, so the percent in the title bar stays fresh while you work in a terminal. A short line such as 5h 23% · 7d 41% also shows at the bottom of the terminal. If your own settings already name a status line, the studio does not take its place and says so. The panel of VS Code never calls a status line, so it cannot help there. See Your limits in the title bar.

What is partial today

• These entries go into Claude Code's settings, so they concern Claude Code sessions.
• The guard is written only when you click for it.
• The status line was not yet seen working in a real terminal session.

Small tips

Questions