Pancho
My personal agent system, designed as a product: one source of truth, daily rituals and an agent that runs on a server. It is how I work.
- Claude Code
- Obsidian
- Node.js
- Docker
- Caddy
- n8n
- Telegram Bot API
Who remembers what happened on Tuesday?
Ten projects, a job, a studio and an AI that starts every session with no memory. The context lived in my head and in scattered chats, and every agent I asked for help started from scratch. I wanted a system that held the context for me, without turning me into its administrator.
- 01One source of truthA plain-text vault, versioned, read by people and agents alike.
- 02Rituals instead of featuresA morning briefing, an evening close, a weekly review: cadence, not willpower.
- 03An agent that lives on a serverIt runs on its own, with the PC off, and talks to me over Telegram.
- 04One method for every repoEvery work session opens and closes reading and writing the same state.
It changed my role: less code by hand, more defining what to build and directing agents. This portfolio was built that way.
Pancho is how I think about and operate software with AI today. An Obsidian vault, versioned in git, is the single source of truth for my projects, work and life, read by people and agents alike. An agent runs on a server with fixed rituals (a morning briefing, an end-of-day close, a weekly review) and a watchdog that alerts exactly once when something breaks. A methodology kit, installed in nine repos, opens and closes every work session reading and writing that state. I designed it as a product with a demanding user: me.