saved
Ultimate: a coding agent each project builds into
Hraness wrote this summary from a saved copy of the source. Quotations are taken word for word from the source.
gist
Daniel Griesser's Ultimate runs Pi's coding agent in a local web UI and lets each project build its own tools, panels and subagents into it. Those extensions, agents, skills and full-screen surfaces live in a committed .ultimate/ folder and hot-reload during the conversation. Ultimate is built on Pi Durable, which writes the conversation, every tool call and every subagent to SQLite before showing them, so it can rewrite its own UI and core without losing its place. The MIT-licensed TypeScript repository, created October 1, 2026, is a personal project whose issues and pull requests go unreviewed.
ideas
- The project, not the user, owns the specialization. Because .ultimate/ is part of the repository, everyone who opens the project boots the same agent, and Ultimate asks once before using a project's setup since project extensions run code.
- Durable state makes self-modification safe. After a change in server/, a restart boots and type-checks a new process next to the old one, the conversation carries on in the new generation, and a failed boot rolls back.
- Every built-in starts switched on. Subagents, plans, documents, automations and remote access ship enabled, and any of them can be disabled per machine in ~/.ultimate/settings.json or per project.
- Work is organized as conversation trees. Each root keeps a read-only context; @ultimate starts coordinator branches that inherit it and compacts that context without deleting history.
- It is shared as inspiration, not as a product. Griesser changes fundamentals without migration paths and points anyone who wants stability to a fork.
quotes
“A coding agent you specialize for the project you work on.”
“Ultimate asks once before it uses a project's setup, because project extensions run code.”
“A failed boot rolls back.”