Claude-Code

Within a few weeks, two open-source tools have set out to solve Claude Code's memory problem. But they don't solve the same problem — Graphify builds a code graph, MemPalace stores the conversation.

Anthropic has released Claude Opus 4.8: same price as 4.7, a clear jump in coding and reasoning, a measurably lower tendency to let its own code flaws slip by, and dynamic workflows with hundreds of parallel subagents.

Bonus article of the series — how the byhaushalt demo parser holds up against two independent sources: the official EPL PDFs from the Bavarian finance ministry and the interactive budget diagram at stmfh.bayern.de. Σ revenues and Σ expenses match the PDF Σ to the cent; the residual difference against STMFH is data-vintage-related.

Article 10 of the series — how a Vite SPA in the repo becomes a live site on a custom subdomain. Branch protection for solo projects, a Bash script that fills the pages branch via git worktree, custom domain via DNS CNAME plus .domains file, HTTPS via Let's Encrypt. And why CI deliberately gets its own follow-up article.

Article 9 of the series — three hooks for byhaushalt: PostToolUse formats after every edit, PreToolUse blocks commits with debug leftovers, Stop runs fast tests but only for changed layers. Why an overly aggressive Stop hook does more harm than good, and why Playwright belongs in CI, not in a hook.

Article 8 of the series — Markdown spec as E2E test contract: Claude reads the user flow, explores live in the browser via Playwright MCP, finds robust selectors, and writes the Playwright test. Three specs, three tests, three baseline screenshots.

Article 7 of the series — two MCP servers, one project configuration: Context7 fetches current library documentation directly into the editor before Claude has to guess. Plus a shadcn/ui migration and a chart-builder skill that calls Context7 deliberately.

Article 6 of the series — three worktree branches, three visualizations over the same data model. Treemap, sunburst, and Sankey compared side by side rather than guessed at sequentially. Plus: why the decision in the end was not against two losers, but in favor of a switcher.

Article 5 of the series — v0.4 delivers three JSON files, not a data model. A plan file with three tasks and parallel subagents builds schema, normalization, and property-based tests. Plus: what format inconsistency teaches about parallelization.

Article 4 of the series — three slash commands make the parser repeatable: /parse-epl for any Einzelplan, /check-totals with built-in pytest, /diff-vs-gesamt for comparison against the full budget. Plus: what xfail reveals about parser gaps.

Article 3 of the series — the first parser code for byhaushalt takes shape via TDD: a custom skill with trigger description, uv setup, six tests before implementation, and how the sum consistency test catches hallucinations in PDF parsing.

Article 2 of the series — before byhaushalt sees its first parser code, Claude Code maps the PDF structure of the Bavarian budget plans. Plan Mode, Explore subagent, and Architecture Decision Records as tools for exploring before implementing.

Article 1 of the series — we install Claude Code, set up the byhaushalt repo, write the first memory file, and pin down what the agent has to follow in every session. Plus: permissions, source data, the first day.

Prologue · Series: Agentic Coding with Claude Code. Anyone reading tech newsletters, conference keynotes, and tool landing pages this year runs into two terms sold with identical promises: Vibe Coding and Agentic Coding. The future of programming, they say.

Claude Desktop registers a Native Messaging bridge in seven browser directories without asking — even in browsers that aren't installed. What it means technically, why it violates the ePrivacy Directive, and why Anthropic of all companies is squandering trust here.

An independent look at GPT-5.5, released April 23, 2026. What the numbers really say, where Claude Opus 4.7 still leads, and why the pricing trajectory should worry developers.