What I build
An Omarchy desktop (Arch + Hyprland) on a ThinkPad, plus a small local agent fleet. AI helps with desktop questions, a knowledge vault, and one job at a time — I still say yes before anything writes.
Agents & harnesses
- opencode-zen (current): Everyday coding agent for the Omarchy tree; OpenCode with Big Pickle.
- Grok Build TUI (current): Default Omarchy coding agent; Buckeroo for Omarchy Q&A.
- grok.com (current): Writes a single brief into a Google Drive inbox; I do not paste it into the agent.
- Herdr (current): Persistent panes for those agents and a few sibling roles.
Apps
- Zen Browser (current): Default browser.
- Obsidian (current): Johnny.Decimal vault for machine and lab notes.
- Neovim (current): Default editor.
- Google Drive (current): Inbox for grok.com briefs.
- NotebookLM API (current): Context gathering and information graphics.
Models
- Big Pickle (current): Used through the opencode-zen TUI.
- Grok 4.6 (configured): Used through the Grok TUI.
Terminal
- foot + tmux (current): Default Omarchy terminal; floating terminal and Herdr panes.
Machines
- ThinkPad X1 Yoga Gen 7 (current, local): Convertible laptop running Omarchy and Hyprland.
Skills
- Omarchy (current): Desktop Q&A from live config and packaged docs; edits wait for an explicit yes.
MCP connections
- mysetup (current): Maintains this setup page through the agent.
- johnnydecimal (current): Johnny.Decimal system docs.
- graft (current): Local code graph for the Buckeroo tree.
- NotebookLM (current): Same NotebookLM API, used from the agent for grounded context.
How I work
- grok.com writes one brief to a Google Drive inbox; the laptop agent picks it up from there after an explicit yes.
- opencode-zen with Big Pickle handles the Omarchy/OpenCode tree; Grok TUI handles Buckeroo.
- NotebookLM API is for gathering context and making information graphics.
- Desktop and config changes are proposed first, then applied only when I agree.