Lazyagent banner
chojs23 chojs23

Lazyagent

AI community

Description

Watch what your ai coding agents(claude, codex and opencode) are doing on your terminal and browser.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

lazyagent

lazyagent lazyagent

`lazyagent` is a tui/web app for watching what ai agents are doing. You can inspect projects, sessions, agents, subagents, tools, prompts and outputs in one place.

It is built for day to day observability. You can see which session belongs to which project, which agent or subagent is active, what tool ran, and what happened next.

It also helps you check whether each agent is doing the work that fits its role, so it is easier to spot when a run goes off track.

lazyagent

You can check token usage breakdowns for each session, so you can see how many tokens were spent on the model, how many were saved by cache reuse, and how many were spent on cache creation.

Features

  • Multi-runtime support -- Support Claude, Codex, and OpenCode sessions
  • Subagent hierarchy -- See which agents spawned which subagents, displayed as a visual tree.
  • Event stream with filtering -- Filter events by type (tool, user, session, system, code) or by agent. Full-text search across event payloads.
  • Syntax and diff highlighting -- Code blocks and diffs in event payloads are syntax-highlighted for readability.
  • Web UI -- A read-only browser dashboard with the same data as the TUI, launched with lazyagent --web.

lazyagent is still early in development, some breaking changes may happen.

Installation

npm

npm install -g @chojs23/lazyagent

Or run without installing:

npx @chojs23/lazyagent

Homebrew

Install from the Homebrew tap with:

brew tap chojs23/homebrew-tap
brew install --cask lazyagent

Go install

go install github.com/chojs23/lazyagent/cmd/lazyagent@latest

Nix flake

These commands build the repository through its flake. The binary version comes from the repo `VERSION` file, while the exact source you install depends on