Regente is open source under MIT.

Regente started as a local coordination backplane for already-running coding agents. Today the source is public: desktop app, CLI, MCP bridge, session hooks, local server, coordination engine, tests, docs, and this website. The repository stays focused on runnable source; contribution and security guidance now live in these website docs.

The repo

The public repository is https://github.com/suhaanthayyil/regente. The code is distributed under the MIT License. The Regente name and logo remain trademarks, but the software itself is open for use, copying, modification, distribution, and contribution under MIT.

git clone https://github.com/suhaanthayyil/regente.git
cd regente
npm install
npm test

What is public

The repository includes the local-first engine that owns claims, fences, messages, handoffs, tasks, context, GitHub/CI routing, adapter installation, hook repair, and dashboard state.

bin/regenteThe CLI for humans and scripts.

bin/regente-mcpThe MCP stdio bridge agents call directly.

bin/regente-hookSession hooks for join, heartbeat, guard, and stop events.

server/regente-core.jsThe locked local coordination engine.

desktop/The Electron desktop command center.

site/The Astro website and public docs.

tests/Smoke, MCP, signing, queue, routing, orchestration, and concurrency tests.

What stays local

Regente does not need a hosted service to coordinate your repo. Coordination state lives in .regente/. The local HTTP server binds to loopback by default. GitHub sync, Slack alerts, Discord alerts, and planner model calls are explicit operator-configured integrations.

How to contribute

Start with the contribution guide and keep changes honest: public docs should match real CLI commands, MCP tools, adapters, and dashboard behavior. Security issues should be reported through the security guide, not filed as public issues.

npm test
npm --prefix site run build
git diff --check

Get Regente

Join the waitlist GitHub repo

← All posts