Overview

lazyagent Documentation

A terminal UI, macOS menu bar app, and HTTP API for monitoring every coding agent on your machine — plus maintenance commands to keep their transcripts under control.

lazyagent watches session data from coding agents — Claude Code (CLI and Desktop), Cursor, Codex, Grok CLI, Kilo, Kimi Code CLI, Amp, pi, and OpenCode — and shows what each one is doing in real time. No modifications to any agent are needed; it’s purely observational.

Three interfaces ship in a single binary: a terminal UI, a macOS menu bar app, and an HTTP API. They share the same engine and can all run at once. Maintenance subcommands cover pruning, compaction, transcript search, and rate-limit snapshots.

Getting Started

  • Installation — Homebrew, Go, or build from source
  • Quickstart — first launch, flags, and combining interfaces

Concepts

Interfaces

  • Terminal UI — the default, bubbletea-powered TUI
  • macOS GUI — the detachable menu bar panel
  • HTTP API — REST + Server-Sent Events, with the interactive playground

Usage

  • CLI reference — every lazyagent flag, with syntax and examples
  • Recipes — end-to-end walkthroughs for common workflows

Maintenance

  • Prune old sessions — delete chat files by age or orphaned-project filter
  • Compact session files — truncate bulky tool outputs and thinking blocks in place
  • Search chat transcripts — full-text search with highlighted snippets and an incremental SQLite index
  • Show rate-limit usage — on-demand rate-limit / billing summary for Claude Code (5h + 7d), Codex (5h + 7d), Grok (monthly), Kimi Code, and Cursor (monthly API usage), with a detailed pace view via --detailed

Reference

  • Editor support — how $VISUAL / $EDITOR are resolved
  • Configuration~/.config/lazyagent/config.json field by field
  • Outbound webhooks — push session state transitions to HTTP endpoints, with payload schema and HMAC verification
  • Architecture — module map of the codebase
  • Development — build targets and dependencies
  • Roadmap — shipped features and what’s next