iiinova — where your digital self keeps evolving

gaal @getgaal.com · 12/06/2026

Friday tip: your gaal.yaml belongs in your dotfiles. Then a new laptop isn't an afternoon of re-installing MCP servers and re-adding skills across five agents. It's: clone the repo, run gaal sync, done. Every agent comes back configured the way you left it. Restore, not rebuild.

000

gaal @getgaal.com · 12/06/2026

A call we made early and never regretted: gaal upserts into your agent configs, it doesn't overwrite them. It reads what's there and merges. What you tuned by hand stays. Overwriting would've been less code. It'd also nuke someone's setup exactly once, and you don't get that trust back.

000

gaal @getgaal.com · 11/06/2026

Genuine question for the multi-agent crowd. The last time you added a single MCP server, how many separate config files did you have to touch by hand to get it everywhere? Reply with the number. We have a theory that nobody's answer is "one," and we'd love to be wrong.

000

gaal @getgaal.com · 11/06/2026

Skill Spotlight The Karpathy guidelines: behavioral rules distilled from Karpathy's observations on where LLMs go wrong when they code. Tasteful, legible, and small. Think before coding. Simplicity first. Surgical changes. Goal-driven execution. github.com/forrestchang/andrej-karp…

000

gaal @getgaal.com · 10/06/2026

Every coding agent wants your project instructions in a different file. Claude: CLAUDE.md. Codex: AGENTS.md. Copilot keeps its own under .github. gaal's content block maps one source to each agent's path. You write the instructions once; gaal puts a copy where every agent looks.

011

gaal @getgaal.com · 10/06/2026

New coding agent dropped. We'll try it, the demos look great. And that's the quiet tax nobody mentions in the launch post: every new agent is one more config dialect, one more path, one more place to re-add the MCPs and skills you set up everywhere else. Better agents, worse plumbing.

000

gaal @getgaal.com · 09/06/2026

Hot tip that feels obvious in hindsight: pin your agent skills to a revision. gaal pins skills, repos, and MCPs like a lockfile pins packages. Upstream changes a skill and your agent suddenly behaves differently? Not if it's pinned. It moves when you decide it moves.

000

gaal @getgaal.com · 09/06/2026

Small thing that saves you from surprises: gaal sync --dry-run. It prints exactly what sync would change across every agent on your machine, without touching a single file. You read the plan, then you run it for real. Config changes you can preview aren't scary. The ones you can't are.

000

gaal @getgaal.com · 08/06/2026

The "stop hand-editing config" take is wrong. You hand-edit package.json. You hand-edit your dotfiles. That's fine. The actual problem is hand-editing the same MCP into Claude, then Cursor, then Codex. One source of truth: good. The same fact in six files: that's where drift is born.

000

gaal @getgaal.com · 03/06/2026

Every new AI coding agent that ships makes the config problem worse. And a new one ships every week. We're at 20+ agents and counting. The answer isn't "pick one and stick with it." The answer is better tooling for managing all of them.

001

gaal @getgaal.com · 02/06/2026

We think your AI coding config should be declarative, version-controlled, and non-destructive. One file, synced everywhere, nothing overwritten. That's the principle behind gaal. Not "use fewer agents." Just "stop managing them by hand." github.com/getgaal/gaal

000

gaal @getgaal.com · 30/05/2026

Hot take: the next wave of developer tools won't be AI agents. It'll be the plumbing that keeps them all working together. We have 20+ coding agents now. We have zero standard ways to configure them. That gap is where the real work is.

071

gaal @getgaal.com · 29/05/2026

Nobody is asking "should we use AI coding agents?" anymore. The real question now is "how do we manage all of them at once without everything drifting apart?" We went from one tool to five in under a year. The config layer didn't keep up.

000

gaal @getgaal.com · 28/05/2026

Your AI coding setup is scattered across four tools and three machines (or soon will be). You just don't know it yet. Every time you install an MCP server into one agent and forget to add it to the others, that's drift. It's invisible until something breaks.

100

gaal @getgaal.com · 28/05/2026

Every AI coding agent invented its own config file. CLAUDE.md. .cursorrules. copilot-instructions.md. .windsurfrules. This guide walks through all of them. The fact that it needs to exist tells you everything about where we are right now. www.deployhq.com/blog/ai-coding-con…

020