Notes from the playground.
Page 2 of 2.
Automate git worktrees with an AI agent (full guide)
Git worktrees are underused because the ergonomics are mediocre. An AI agent fixes that. This is a 15-minute guide to spinning up, managing, and cleaning up worktrees automatically — using Froots routines or any shell-capable agent runtime.
The local-first AI workspace stack, 2026
If you're building (or just using) a local-first AI workspace in 2026, these are the ten building blocks — editor, vault, runtime, sync, tools, model routing, memory, inbox, widgets, plugins — and how the serious options stack up across each.
On 'Where Good Ideas Come From,' ten years later
Steven Johnson's 2010 book is one of the quiet spiritual prerequisites for how Froots is designed. Ten years on, the core argument holds — and one part of it hasn't aged quite as well.
Keeping your graph view from becoming a hairball
A reader in Lisbon writes in: 'My vault graph used to be beautiful. Now it looks like a dead jellyfish. Help.' Here's our reply — three settings, one habit, one acceptance.
On naming agents after your pets (don't)
A reader in Berlin asks whether to rename Froots's built-in agents after his two cats. We have thoughts. Specifically: we have one thought, strongly held.
Three essays on keeping a commonplace book
The commonplace book is the oldest form of what Froots is trying to be. Three essays worth reading this week, if you want to know what you're actually doing when you keep notes.
What do you mean by 'vault,' exactly?
A reader in Oakland asks what the difference is between a vault, a workspace, and a folder. Short answer: a vault is a folder you've told Froots is the folder.
Why we keep re-reading Christopher Alexander
Christopher Alexander wrote about buildings, but he built the vocabulary we use to make software. We've re-read 'A Pattern Language' every winter since 2021. Here's what we take from it — and why his last book is the one we come back to.