vibe-log-cli
A CLI that analyzes Claude Code and Codex sessions: standup summary, productivity report and tips in the status line
- 339 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads local Claude Code and Codex sessions, which can contain code fragments and secrets
- Hooks run CLI commands on every prompt and session start
- With cloud sync on, session data goes to the vibe-log.dev server
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/vibe-log-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads local Claude Code and Codex sessions, which can contain code fragments and secrets
- Hooks run CLI commands on every prompt and session start
- With cloud sync on, session data goes to the vibe-log.dev server
This is third-party code. Review the repository files before installing.
What it does
vibe-log-cli reads local Claude Code and Codex sessions and turns them into three things. The first is a daily standup summary: what you worked on, what you finished and what comes next. The second is an HTML productivity report for a chosen period and chosen projects. The third is a coach in the Claude Code status line that scores your prompt and suggests the next step. Analysis runs locally: the CLI launches your own tool through ACP or the Claude Code SDK, and the data stays on your machine. The coach attaches through the UserPromptSubmit hook. It has three personalities: the sharp Gordon, the supportive Vibe-Log and your own. Cloud sync to the vibe-log.dev dashboard is a separate option. Before sending, a privacy layer strips code and secrets, and automatic sync in Claude Code is set up with SessionStart and PreCompact hooks.
Who it is for. For developers who work in Claude Code or Codex and want to see what their sessions produced, prepare standups and improve their prompts.
Good fit when
- In the morning you need a two-minute recap of yesterday's Claude Code work for a standup
- You want an HTML report of the week's work for specific projects
- You want a quality hint for every prompt right in the status line
- You want to track the trend of your sessions on a dashboard and accept cloud sync
Not a fit when
- You need token and cost analytics: dedicated cost counters cover that
- Company policy forbids sending any session data off the machine, even sanitized
- You work in Cursor or VS Code: support is only planned
- Hooks are forbidden in your environment: the coach and auto-sync work through them
Example request
Run npx vibe-log-cli@latest and prepare a standup summary from yesterday's sessionsLimitations
Claude Code and Codex are supported. Codex auto-sync is experimental and send-only, and there is no coach or status line for Codex. Cursor and VS Code are listed as plans. Node.js is required. The cloud dashboard accepts up to 1000 session analyses a month on the free tier, and sign-in goes through a GitHub account. Local analysis uses your own agent, so it spends your own limits. Summaries and reports are built from the available local sessions, and for very long sessions the CLI truncates them while keeping timing data.
How to disable. Open npx vibe-log-cli and turn off the status line and hooks in the menu: your previous status line setup comes back on its own. The ~/.vibe-log folder with analysis results is deleted by hand.
FAQ
How do I install vibe-log-cli?
The command npx vibe-log-cli@latest opens the interactive menu right away. No separate install is needed, only Node.js.
Does my data leave my computer?
Local summaries and reports are built on your machine. Cloud sync is optional: a privacy layer strips code and secrets first, and only generalized patterns reach the server.
What does the status line coach do?
The UserPromptSubmit hook passes your prompt to local analysis in Claude Code. The score and advice are saved to ~/.vibe-log/analysis, and the status line reads them from there.
What happens to my existing status line?
On install the CLI backs it up, and on uninstall it restores the original setup.
Which hooks does auto-sync use?
In Claude Code these are SessionStart, which syncs earlier sessions at startup, and PreCompact, which syncs the session before context compression. In Codex they are SessionStart and Stop.
Discussion
No questions or reviews yet.
Related
CLI toolsA Claude Code plugin: a status line with context, 5-hour and 7-day limits, cost and usage of Codex, Gemini and z.ai
cc-lens
Claude Code Lens (cc-lens)
Local Claude Code analytics: a dashboard of sessions, tokens, cost and projects from your ~/.claude data, no cloud
A statusline for Claude Code: token and cost usage, context left, rate limits and git branch in four styles and six themes
Token and cost reports for Claude Code, Codex, Gemini CLI and other agents from local logs, by day, month and session
A customizable status line for Claude Code: model, git branch, context, usage limits and other widgets
A skill that builds an anonymized developer profile and a vertical poster from local Claude Code and other CLI history
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| vibe-log-cli (this entry) | no | 339 | |
| ccusage | no | 19,251 | counts tokens and cost from logs, with no standup summaries |
| Claude Code Usage Monitor | no | 8,782 | terminal monitor of usage in the 5-hour window |
README in short
The author publishes builds to npm with provenance and SHA256 checksums, so you can match the package against the source code. Diagrams in the docs show how the status line and local reports get their data from your agent.