Show HN: 예, 에이전트를 위한 또 다른 Htop

Early stage software. Expect breaking changes, incomplete data, and rough edges. Use at your own risk. workpulse is a local-first terminal monitor (like htop) for coding agents. go install github.com/juanpabloaj/workpulse/cmd/workpulse@latest go run ./cmd/workpulse The initial MVP focuses on: - Claude sessions discovered from ~/.claude - Codex sessions discovered from ~/.codex - Gemini sessions discovered from ~/.gemini - OS-level process correlation - A terminal UI that combines process data with session metadata, tool activity, and token usage workpulse is not trying to read agent reasoning. It is trying to expose operational truth: - which agents are active - which repo and branch they are working on - which tool they are using - whether tool calls are failing - how many tokens they are using - whether the process is still alive, idle, blocked, or done ~/.claude/sessions/*.json ~/.claude/projects//.jsonl ~/.claude/projects///subagents/*.jsonl for subagent counts only ~/.codex/sessions/**/rollout-*.jsonl ~/.gemini/tmp//chats/session-*.json ~/.gemini/projects.json for project-to-path mapping~/.gemini/history/*/.project_root as fallback CWD resolution ps lsof forcwd - discover local Claude, Codex, and Gemini sessions - parse real metrics already available in local session artifacts - correlate sessions with live processes when possible - render a TUI with a main table and a detail pane - no cloud service - no MCP dependency - no vendor instrumentation beyond what the local tools already write - no inferred quality score in the main view Some local agent directories contain shell snapshots and other sensitive material. workpulse should never render raw environment snapshots or secrets in the UI. The MVP intentionally avoids reading those files for display. - Codex live session correlation is heuristic because Codex does not expose a simple active-session PID index similar to Claude's ~/.claude/sessions/*.json - The current process collector is implemented around ps andlsof , which is practical for macOS and Linux but not yet tuned for Windows - Token extraction is currently best-effort and depends on which fields are present in each local artifact - Maybe other names could have been atop or yaat (yeah another agent top). The name "workpulse" is meant to evoke the idea of taking the pulse of your coding agents, monitoring their health and activity in real time.