claude-code

A log check flagged 16 of 31 Claude Code turns that ended on a failing test. None ended on a false claim; it missed the one that did. Why, and 3 rules to try.

My insurer wouldn't renew over the roof's age. How I used AI, mostly Claude, to replace the policy within 45 days, pick a roofer and close two permits.

I'm testing whether my agent operator's rules and tools work better as a shared kit in project sessions: why it's worth trying and what the trial must show.

How I use local Codex and Claude Code session logs to recover decisions, resume unfinished work, watch active tasks, and turn patterns into handoffs.

I built Karpathy's LLM wiki pattern into Command: 134 provenance-tagged pages, a gate that blocks fabricated quotes, and a human-gated publish step.

Claude Code deletes session transcripts older than 30 days by default. Raise cleanupPeriodDays in ~/.claude/settings.json to stop it; lost logs stay lost.

The key design decisions in Command, my Claude Code operator: a free deterministic watcher, per-repo config it writes, and a success criterion on every fix.

Coding agents read prose design specs as ground truth, and specs drift. chat-arch's CI guard checks each palette row as a claim; here's what it catches.

Two patterns from Anthropic's harness research: why agents can't grade their own work, and when to prune harness complexity as models improve.

Fixing three Claude Desktop failures on Windows: Cowork's 'VM service not running', an empty Google Drive connector, and 'This isn't working right now'.

Subagents, skills, CLAUDE.md orchestration, headless runs and state management for Claude Code multi-agent systems, with 50 claims checked against the docs.

After 1,500+ commits of AI-paired development, I use three tools with distinct roles. What stuck, what didn't, and how GPT caught a security bug in a PR.