ALADEEN

See exactly where your coding agents get stuck.

Claude Code · Codex · Gemini · opencode

$ npm i -g aladeen

ALADEEN // PRODUCT DEMO

Video not found — drop aladeen-demo.mp4 into this folder and refresh.

Real data from 199 sessions

199

agent sessions
ingested

recurring failure
patterns found

21×

the same error,
across 3 projects

1710

edits to one file
in a 2-minute session

What those numbers actually mean

▸ Codex kept hitting the same PowerShell tool error — 21 separate runs, three different projects, exact same fingerprint. Nobody noticed until the report surfaced it. f62bd339

▸ One catastrophic lint→fix-lint loop: the agent edited a single file 1,710 times in two minutes, racking up 1,930 worktree collision errors before giving up. 690cbbfe

▸ The fix was one line: run npm install inside the git worktree before the lint step. Aladeen found it, cited the source line, and marked it KNOWN FIX. KNOWN FIX

▸ When there isn't enough history yet, Aladeen says so. No invented fixes. No confidence theater. "Not enough history yet" is an honest answer. TIER 4

Three commands

STEP 01

aladeen ingest

Read your session logs

Points at your existing ~/.claude/, ~/.codex/, or opencode log dir. Reads everything locally — never uploads, never phones home. Parses tool calls, errors, timings, and file edits from raw session JSON.

STEP 02

aladeen report

See the recurring patterns

Groups sessions by error shape, not just outcome. Shows you which failures repeat, how often, and across which projects. Edit loops, tool failures, auth errors — all surfaced with a fingerprint you can drill into.

STEP 03

aladeen remedy <fp>

Get an honest fix

Four tiers: KNOWN FIX with file:line citation, medium/low confidence suggestions, or a frank "not enough history yet." Read-only by default — it suggests, and on --apply runs a proven fix in an isolated worktree. You stay in control.

Your sessions never leave your machine.

100% local Reads from your existing log dirs. No servers, no accounts, no telemetry.

Read-only by default Never writes to your session files, never touches your working tree. By default it only observes.

Runs only on your command Suggestions are read-only. With --apply, proven fixes (today: dependency repairs) run in a throwaway worktree — your tree untouched, nothing merged.

Free forever npm i -g aladeen and you're done. No paywalled features, no SaaS tier.

■ ALL DATA STAYS ON DISK ■