Every session on your PC,
in one list.
AigoPilot finds your Claude Code and Codex sessions by itself, including the ones you started in VS Code or a terminal, and shows what each one is doing right now.
Once you run more than two or three agents, the hard part stops being the code. It becomes remembering which terminal had the session that asked you something twenty minutes ago. This part of AigoPilot deals with that. It reads the session files Claude Code and Codex already write, so there is nothing to import and nothing to set up.
Open the app and your projects are already there. AigoPilot reads the session files that Claude Code and Codex keep on disk, so sessions started in VS Code, in a terminal or in the Codex desktop app all show up. On a PC with 3,173 session files (2.6 GB) the first scan took 16 seconds. A rescan with nothing new takes about 16 milliseconds.
Each project is a card that tells you whether anything in it is working, and how many sessions are busy. Sort the list by latest activity, or by how much of this week's usage limit each project has used.
Open a project and its sessions are laid out by how alive they are. Active ones get big cards, idle ones get small ones, and old ones fold into a single archived card you can open when you need it. Every card shows the first prompt, the last prompt and the current state. Usually that is enough to remember what a session was for.
“Finished, and you have not looked yet” looks different from “waiting for your answer”, and both look different from “waiting for permission” or “hit its usage limit”. A session whose process died says it stopped unexpectedly instead of sitting there looking idle.
The state comes from Claude Code's official hooks, from whether the process is still alive and from whether the transcript is still growing. Nothing is guessed from terminal text.
Questions, permission requests, finished work and sessions that edited an instruction file all collect in one column. Each row shows how many files that session wrote. Pin the rows you care about and they stay at the top.
Full-text search over every session on the machine, in any language. Spelling variants still match, so Persian and Arabic letters or digits typed either way find the same conversation.
Give a session a name you will recognise next week. A name you choose always wins over the one the AI made up. Pin the few that matter.
Sessions started by your own scripts, and the internal reviewer threads Codex creates, are marked as automated and hidden unless you ask to see them. The list stays about your own work.
A session opens at its latest turn and follows new text as it arrives. Scroll up to read something and the following stops right there. One button takes you back to the end.
Between paragraphs you see short rows such as “Edited 2 files, ran a command, +11 -4”. Open one to see the exact commands and files. It works the same way for Claude Code and Codex.
While a session works, a line under it shows the time since your prompt, the tool it is using right now (or the heading of Codex's latest reasoning) and any background tasks. When the turn ends it tells you how long it took, for example “Worked for 1 min 2 s”.
Each prompt gets a plain list of what is done, what is happening now and what is left, written in your language. Code stays out of the way until you want it. This works for Claude Code sessions run from AigoPilot; a session running in your terminal does not get one.
A list of the files the session itself wrote, with lines added and removed, and the diff of each one a click away. Git is only read, never written to. In a folder without git, the change is rebuilt from the session's own edits.
One bar splits a session's context into its parts: system prompt, tools, MCP tools, agents, memory files, skills, messages and free space. A mark shows where automatic compaction will start. For Codex you see the total.
The top of every session shows how much of the context window it uses, and what the session and its last turn would cost at API prices. Past 60 percent of the window it changes colour and suggests starting fresh.
See every CLAUDE.md, AGENTS.md, memory file and settings file that shapes a session, in the order the agent loads them, and which session last wrote each one. If another session changed one you have not seen yet, you are told. A Markdown instruction file can be switched off and on again.
When a session edits an instruction or settings file, it jumps to the top of your waiting list. You see the change line by line and choose: put it back, keep it, or open it in your editor.
A web address in an answer opens in your browser. A file the agent mentions opens in a pane inside AigoPilot, even when it sits on another of your computers, with a button to open it in its usual program. Programs and scripts are only shown in their folder. They are never started.
One click opens the project in its IDE, or brings the editor window forward if it is already open. You can keep working there whenever you like; sessions you start in the editor show up in AigoPilot too.
Open the editor on the tab of one particular session, instead of only on the project.
AigoPilot lives in the tray. Closing the window does not stop any session, because a small background engine keeps them going. Open the window again and everything is where you left it.
The interface is in English. Pick one of four themes, one light and three dark, and one of four text sizes.
The interface is in English today. It is built to take any language, right-to-left ones included, but no other language is offered yet.
Yes. It reads the session files Claude Code and Codex write, wherever a session was started: VS Code, a terminal or the Codex desktop app. They appear in the same list as the sessions started from AigoPilot.
No, it only reads them. The one exception is moving a project to another of your computers: its transcripts are then added to the CLI's folder on that computer, next to what is already there, and nothing existing is changed.
Type in AigoPilot's search box. It searches the text of every Claude Code and Codex conversation on the machine, in any language.
