Agent Statusline
- Updated July 18, 2026
- alleneubank/agent-statusline
agent-statusline is a Claude Code plugin marketplace that ships a Zig statusline renderer and activity hooks so developers can monitor agent session context in one terminal line.
About
agent-statusline is a Claude Code plugin marketplace built around a Zig statusline binary that formats JSON snapshots into a single resilient line. Developers reach for it when they want git, model, goal, and activity context visible during Claude Code or Codex sessions without brittle shell scripts. Activity hooks persist lightweight state for prompt and stop events under a configurable state directory.
- Zig renderer reads JSON stdin and prints one status line
- Crash-free segments with Claude and Codex glyph support
- Hooks record UserPromptSubmit and Stop timestamps
- Goal and token budget segments for Codex-style payloads
Agent Statusline by the numbers
- Data as of Jul 19, 2026 (Skillselion catalog sync)
/plugin marketplace add alleneubank/agent-statuslineAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | July 18, 2026 |
|---|---|
| Repository | alleneubank/agent-statusline ↗ |
How do you see model, git, goals, and recent agent activity in Claude Code without a fragile custom status script?
Renders a fast Zig-based Claude Code status line with git, model glyphs, goals, and activity hooks.
Who is it for?
Developers running Claude Code or Codex who want a spec-driven, crash-free statusline with debug capture options.
Skip if: IDE users who do not use command-backed statuslines or cannot install the Zig-built binary should skip it.
What you get
Each render produces a formatted status line and optional replay artifacts under STATUSLINE_CAPTURE_DIR.
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
FAQ
What runtime builds the statusline?
A Zig 0.16+ binary with no external dependencies reads JSON from stdin per the README.
How is activity shown?
Plugin hooks record UserPromptSubmit and Stop with timestamps stored under STATUSLINE_STATE_DIR or XDG paths.
What happens on segment errors?
Segments degrade gracefully and the process still exits 0 per the crash-free design.