Claude Code setup I built for a bike workshop's 20-year-old classic
Points: 1 # Comments: 0 Claude Code setup I built for a bike workshop's 20-year-old classic Coverage based on HN Claude/Codex/Fable reporting.
By Dillip Chowdary • Sep 01, 2026 • Source: HN Claude/Codex/Fable
What happened
A developer has shared details of a custom Claude Code implementation designed to manage and update a legacy web application. The project, documented on the marginalia blog, focuses on applying modern artificial intelligence tooling to a classic Active Server Pages system that has served a bicycle workshop for two decades. The project was shared on Hacker News under identification number 49527376, where it received one point and zero comments.
How it works
This

Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Why it matters
How I built a Claude Code system that actually knows how I work Five months of Claude Code building its own tooling, steered by me, across a fleet of machines and a handful of separate codebases — a proper todo database, two-tier memory, and a session routine that runs itself. Most write-ups of AI coding assistants are about a clever prompt or a plugin you can install.
Who is affected
This one's about something slower, and I think more useful: having the assistant build its own tooling over months, in a git repo, tuned to exactly how you work. I've been running Claude Code across a real business for the past five months.
What to watch next
Each its own git repo, all run from the same machines: Proxmox hosts, Linux servers, a few laptops, a work desktop, and an Android phone running Claude Code in a terminal. See the full write-up from HN Claude/Codex/Fable via the source link for quotes and complete context.
Developer Action Items
- ☐ Verify the claim on the official Claude / Android / Linux page (or HN Claude/Codex/Fable), not from this recap alone.
- ☐ Name the surface that moved — API, policy, model, hardware, or commercial terms — before you Slack the thread.
- ☐ Assign one owner a day to read the primary material and decide: this-sprint, this-quarter, or noise.
- ☐ Do not change production on day-one coverage. Watch the vendor changelog and one independent write-up first.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Anthropic upgrades Claude with new Fable 5.1 model, details here
Read →
OpenAI delayed its new model’s development after the Hugging Face hack
Read →
Palo Alto Networks Acquires AI Agent Platform Console
Read →
Frontier models can recover up to 65% of facts they can't directly recall — just by…
Read →
Today's Tech Pulse briefing
Full briefing →
Advertisement