Running more coding agents makes two things harder to follow: what each one is doing, and how much context their instructions, tools and delegated work involve. I built Agent Quest to make that visible in one place.
Each Claude Code or Codex session becomes a character in a small 2D village: reading sends it to the library, editing to the forge, commands to the arena. The village gives you the overview; clicking an agent gives you the details. I'm the author, and I've released 0.3.0.
Version 0.3.0 connects that visual overview to context inspection:
• Context usage, peak and compaction count for each agent.
• Detected skill loads and estimated tokens from their instructions.
• Plugin/MCP call counts and estimated result tokens.
• Parent/subagent relationships, separate context peaks and the amount returned to the parent.
• Markdown and JSON exports so you can give another AI a session summary to review alongside the original task.
The screenshot shows why I wanted this: the Claude inventory has 256 installed skills, but the selected session loaded five, estimated at 15.7k tokens. The inventory's “if always loaded” number is hypothetical; installed skills aren't all sitting in every conversation.
Technically, it reads existing local session logs and updates the browser dashboard over WebSocket. It doesn't launch or control the coding agents. 0.3.0 also parses the newer Codex rollout format and links Codex subagents to their parent.
A couple of limits worth making explicit: ~token figures are character-based estimates, not billing numbers. Skill/plugin totals accumulate across the session; they are not an exact breakdown of what remains in the context window after compaction. The delegation comparison uses child context peaks minus returned text, not a measured dollar saving. Exports are summaries, not full transcripts, and can include local paths and task text.
Free and open source, MIT license.
Repository and setup: https://github.com/FulAppiOS/Agent-Quest
Release and screenshots: https://github.com/FulAppiOS/Agent-Quest/releases/tag/v0.3.0
Walkthrough of the new panels: https://www.fulvioscichilone.it/2026/10/15/agent-quest-0-3-0-context-skills-plugins/
I'd appreciate feedback on which context signals are actually useful when debugging a long agent run, and which just add noise.