vibesenpai
vibesenpai is an open-source Claude Code plugin that reads Claude Code sessions stored locally and identifies where an agent went wrong, showing the user's own words and the relevant turns plus a fix that can be applied. It emphasizes evidence rather than scoring the developer or agent.
At a Glance
- Claude Code users
- Software developers using AI coding agents
- Teams seeking local-first AI-agent observability
- Developers who want evidence-based prompt and workflow corrections
AI Tools by vibesenpai
(1)vibesenpai
Claude Code Session Analyzer
Discussions
No discussions yet
Be the first to start a discussion about vibesenpai
Latest News
Published a do-not-push demo video across the home page, README, and documentation; documentation site also added Umami page-visit measurement.
Released vibesenpai 0.1.0, adding consent-gated model-read previews, recorded/fingerprinted calls, the Status tab, and the Sent tab.
Released 0.0.5 with a Rules tab and persistent records of findings dropped by the lookback gate.
Promoted 0.0.4 from alpha to stable version labeling.
Products & Services
An MIT-licensed TypeScript Claude Code plugin installed through the vibesenpai marketplace. It reads local Claude Code session transcripts, runs free structural checks and optional consent-gated model reads, presents findings in an insights pane, and drafts fixes into the Claude Code prompt box rather than writing files itself.
The side-pane command showing findings, the evidence turns, fixes, rules, status, and sent-call information.
The command for previewing, enabling, or disabling optional model reads; model reads run through the user's own Claude account or API key.
Creates a self-contained offline HTML report containing findings, supporting turns, and fixes.
Market Position
vibesenpai positions itself as a local-first, evidence-oriented Claude Code plugin for post-hoc analysis of agent behavior: it shows the exact user instruction and surrounding turns, rather than assigning a score, and turns findings into an actionable fix. The ClaudePluginHub comparison page places it alongside broader Claude Code toolkits, multi-agent consultation plugins, and workflow/loop plugins; vibesenpai is narrower and specifically focused on diagnosing failures in prior sessions.
Leadership
Founders
Souvik Roy
Creator and primary maintainer of vibesenpai; GitHub identifies the repository's principal author as Souvik Roy (account crozzfire). The repository history shows him authoring the project and its releases; the project's launch description says he created it from frustrations with AI-driven development.
Executive Team
Souvik Roy
Creator and primary maintainer
Principal author of the public GitHub repository and author of the release and documentation commits.
Founding Story
The project was created after its author became frustrated with AI-driven development and wanted a tool that could show concrete evidence of agent failures in existing Claude Code transcripts and suggest a corrective prompt, rule, permission, guard, or test. It began under the name agentsensei and was renamed vibesenpai in the first alpha release.
Business Model
Revenue Model
The plugin itself is open source and its free checks cost nothing. Optional model reads use Claude Haiku through the user's own Claude Code subscription or API key, so the documented cost is usage-based on the user's account rather than a separate vibesenpai subscription.
Pricing Tiers
Local structural checks run without charge.
Runs on the user's own Claude Haiku plan or API key, within about 2 million tokens per day; the documentation gives about $0.26 as an API-price example.
Target Markets
- Claude Code users
- Software developers using AI coding agents
- Teams seeking local-first AI-agent observability
- Developers who want evidence-based prompt and workflow corrections
- Reviewing Claude Code sessions after an agent violated a stated constraint.
- Finding misread requests, overreach, inaccurate claims, and repeated or failed tool calls.
- Turning recurring agent mistakes into project-specific prompt rules, permissions, guards, or tests.
- Monitoring and auditing local AI-assisted software-development workflows without uploading transcripts by default.
- Inspecting history through an offline report.
- Public demo based on test data from claude-code-log