Best practices for building with a local agent
What we learned building GlimpseKit's worked examples with a coding agent on a 32 GB Mac.
Use the computer you have first
Run a task locally when a small model does it well: translating, transcribing, drafting, building a small site. Reach for a large cloud model when the task needs it, and know why. The work stays private, costs nothing per use, and adds no load to a data center.
Keep each phase small
Give the agent one phase at a time, about ten minutes of work. A phase says its goal, what the visitor can do afterwards, the files to read first, and what done looks like.
Write down the facts
A local model has a small memory. Put the exact names, calls and traps it needs in the phase's KNOWN section, checked against the installed versions, so it doesn't have to look them up or guess.
Check in a browser, not only the build
A build that passes can still show a broken page. Every phase of a recipe has a browser check that clicks through what the phase promised.
Mend the recipe while a phase runs
When the agent stumbles, the recipe is usually what to fix: a missing fact, two names that can be confused, a file it wasn't told to read. Fix it at once with gk project:sync, and the next step uses it.
Keep private things private
No personal names, home paths or keys in code or docs. Media made with your Mac's voices stays on your Mac.
Get the docs before you go offline
gk library:fetch puts the documentation an app needs on your machine, so the agent reads current docs instead of guessing from memory.