-
Notifications
You must be signed in to change notification settings - Fork 0
AI Agent Workflow
GNOME Widget Panel provides two different AI widgets:
- AI Agent Usage shows recent activity and usage.
- AI Agent Status tells you when a Claude Code session needs attention.
They solve different problems and support different providers.
The usage graph supports Claude Code, Codex and Gemini CLI. Columns show recent token activity in each provider's colour. Request markers show when prompts were sent. Indicator bars show available rate-limit and context information when the provider exposes it.
Codex is detected from its local session files. Gemini CLI is detected from its local data directory; Gemini token extraction is best-effort and rate-limit data is unavailable. Claude Code requires the widget's local hook setup: open the widget settings and select Configure.
The optional status widget currently supports Claude Code only. Add it from the panel's widget list and configure the Claude hooks from its settings.
The single dot shows the most urgent state across all detected Claude Code sessions:
- Pulsing red — an agent is waiting for permission or attention.
- Pulsing amber — a turn finished and the session is ready for another prompt.
- Solid blue — an agent is still working.
- Dim grey — no open sessions are detected.
Hover over the dot to see the session breakdown.
- Start one or more Claude Code tasks.
- Switch to your editor, browser or another workspace.
- Glance at the status dot instead of repeatedly checking each terminal.
- Return when it pulses red to unblock the agent.
- Return when it pulses amber to review the result or send another prompt.
The widget does not automatically switch windows or answer prompts. It gives you a small, persistent cue so you decide when to return.
Provider data is read locally. Claude Code communicates with the extension through localhost hooks; configuring it writes the GNOME Widget Panel hook scripts and updates Claude's settings while preserving existing hook entries. Usage history is held in memory rather than uploaded by the extension.
Codex and Gemini CLI do not currently provide the lifecycle integration used for reliable waiting/finished detection. They appear in the usage graph, but not in the attention-status widget.