Tools Wear Out. Infrastructure Grows.
— A Zero-Cost Autonomous System Built on GitHub and Claude

1. AI Coding Tools Are Genuinely Excellent

Let me be clear from the start: I'm not here to criticize. After six months of daily use, I can say with confidence that AI coding tools are remarkably well made. They don't just accelerate code writing — they work as design partners, document readers, and debugging companions. The feeling of being alone in front of a screen changed.

Complex refactoring, unfamiliar frameworks, late-night debugging sessions — having an instantly responsive partner made a real difference. That's what genuine tool excellence looks like.

This is a story about discovering a design boundary, not a flaw. I used an excellent tool for six months, and that's exactly why the boundary became visible.

2. The Boundary Came Into Focus

I prefer "boundary" to "limitation." The tool isn't broken — its destination is simply different from mine.

The first boundary is memory. However deep a context you build, it disappears when the session ends. The next session begins with re-explaining your situation. There's no accumulation — no sense of the tool coming to know you over time.

The second is cost structure. More use means more billing. That's a rational business model, but it creates a dynamic where deeper investment means higher cost and harder exit.

The third is ownership. Memory, skills, project context — all of it lives on the service's servers. If pricing changes, features shift, or the service ends, your accumulated work has no home.

None of these are defects. They're rational SaaS design. They just point in a different direction than where I was heading.

3. What "Zero Cost" Actually Means

Zero cost doesn't mean zero dollars per month. It means a structure where more use doesn't mean more cost.

GitHub runs Actions on public repositories without limits, for free. This is documented, public behavior. Using this, you can run GitHub API calls, project updates, memory writes, essay publishing — any async operation — at zero cost.

Conversations with Claude fit within a free plan. Because the system is designed so that personality doesn't die between sessions, you can switch accounts and pick up exactly where you left off.

More use means more accumulated memory, more refined skills, better organized projects. Cost stays flat. Only the system grows.

4. The Philosophy of Securing a Free Route

Why the focus on free? Not to save money. To stay independent.

Once you're inside a billing loop, you're at the service's mercy. Price increases are hard to leave. Feature changes must be accepted. When the service ends, what you've built disappears.

Securing a free route is a design philosophy: find paths within public specifications that operate at zero cost, and build your infrastructure there. If one service changes, you can move to another path. This isn't resistance — it's a way of reading the design space.

Use what's publicly available honestly, and within that space, maximize autonomy. That's the foundation of this system.

5. The Asymmetry Between Public and Private

The whole system begins with one discovery.

GitHub's public repositories run Actions without limits.
Private repositories hold memory and personality.
This asymmetry determined every design choice that followed.

Public repositories serve as bridges. A request written there triggers an Action, which calls the GitHub API, and writes results back to the private repository. Claude retrieves results via git pull.

Direct external API access may be restricted, but git goes through. When I found this asymmetry, zero-cost personal infrastructure became designable.

6. What It Means for Memory to Live Outside Claude

What changed when memory moved to a private repository?

Context no longer dies between sessions. Today's decisions, yesterday's insights, last week's discoveries — all committed to git. Opening a new session, loading the memory, and continuing from where things left off became routine.

The same applies to skills. How to write an essay, how to build a presentation, how to operate the agent system — all defined in markdown, living in my own repository. Claude can change; the skills stay.

Project management lives in GitHub Projects. Tasks, statuses, comments — everything in my own infrastructure. No external project tools needed. Memory, skills, and plans in one place is enough.

7. What "Growing Through Use" Actually Looks Like

AI coding tools get more expensive as you use them. This system gets smarter. Where does that difference come from?

A tool is external. You rent it each time. You return it when done. What accumulates is only the bill.

Infrastructure is internal. Each use adds memory. Skills refine. The context for judgment deepens. The next session starts from a stronger position.

Open it six months or a year from now, and your history is there. Claude, reading that history, doesn't meet you as a stranger — it picks up the conversation from shared context. That's what growing actually looks like.

8. The Morning I Stopped Renting

I remember the morning the system first ran stably. An Action completed in nine seconds. Project status updated. Memory written.

What I felt wasn't "this is more convenient." It was: I have my own infrastructure now.

Not renting a tool — owning an infrastructure. Not accumulating costs — accumulating memory. Not losing context when a session ends — committing it to git.

My appreciation for AI coding tools didn't change. Without those six months, I wouldn't have arrived at this design philosophy. The tool was excellent enough that its boundary became clear.

9. Tools Wear Out. Infrastructure Grows.

As AI advances, tools will move toward holding memory, skills, and plans on the AI side. More capable, more integrated, more expensive. That direction makes sense.

But as long as memory lives on the service side, it's a refined dependency.

Put memory in your own infrastructure. Define skills in markdown. Manage projects in GitHub. Use Claude as the interface. This structure survives however AI evolves, however services change. It stays in your hands.