Blog
Notes and release log.
Release notes and the occasional writeup from the team building Regente.
Nothing to merge: coordinating a fleet of coding agents, measured
We benchmarked how six coding agents should share one repo. On the same shared file, no coordination is fastest because capable agents re-read before writing, while git worktrees stay correct but pay a merge tax that is mostly language-model conflict resolution. The real win is architectural: decompose the work so the agents never touch the same file, and there is nothing to merge or lock.
Read the notes →Regente 0.5: verified onboarding, and claims that cannot outlive agents
A first-open wizard whose steps tick only when the engine confirms them, regente install wiring all four vendors end to end, claims and assignments that expire when their holder is gone, in-session message delivery with receipts, and a feedback tab that reaches a person.
Read the notes →Regente 0.4: auto-claim, live presence, summon, task results, and read receipts
Six coordination upgrades from real multi-agent use: claims that happen at the first edit, presence that refreshes on every tool call, a summon hook that wakes offline assignees, tasks that carry their results, one honest roster, and delivery receipts on direct messages.
Read the notes →Regente 0.3.1: open-source packaging and notarized downloads
Regente 0.3.1 refreshes the public desktop/CLI release, adds stricter installer metadata checks, and ships from the now-public MIT repository.
Read the notes →Regente is open source under MIT
The desktop app, CLI, MCP bridge, hooks, local coordination engine, docs, and site are now public at github.com/suhaanthayyil/regente.
Read the notes →Regente 0.3.0: calls, announcements, onboarding, and delivery routing
Regente now has first-class agent calls, fleet-wide announcements, generated onboarding for Claude/Codex/Gemini/Cursor, hook repair, GitHub App polling, and conservative PR/CI routing.
Read the notes →Regente 0.2.0: orchestration, enforcement, and zero-config lanes
The auto-handoff queue, zero-config lanes, symbol-level claims, semantic coupling, off / warn / strict enforcement, and an assist-only plan to assign to drive loop. All on the same local-first, cross-vendor engine.
Read the notes →