Docs
Contributing to Regente.
Regente is open source under MIT at github.com/suhaanthayyil/regente. The repository is intentionally code-focused: source, tests, scripts, package metadata, and the Astro website. Long-form project guidance lives here in the website docs.
Set up locally
git clone https://github.com/suhaanthayyil/regente.git
cd regente
npm install
npm test
npm --prefix site install
npm --prefix site run buildThe main test suite exercises the local coordination engine, MCP bridge, hooks, queueing, signing, GitHub routing, task assignment, and concurrency paths. The site build verifies every public docs page.
Good contributions
bin/CLI, MCP, and hook behavior should stay thin over the shared engine.server/Core state transitions need focused tests and clear failure behavior.desktop/Desktop changes should preserve local-first assumptions and loopback-only defaults.public/The dashboard should expose real state, not inferred marketing-only status.site/Website docs must match real commands, adapters, MCP tools, and UI behavior.tests/Add regression coverage beside behavior changes, especially for shared engine contracts.Before a pull request
npm test
npm --prefix site run build
git diff --checkKeep PRs narrow and explain the user-visible behavior. If a change touches claims, fences, task transitions, signing, or adapter install/repair, include the exact failure path the test covers.
Accuracy rules
Regente should be described as a cooperative, local-first coordination layer for participating coding agents. Do not claim it is a security sandbox, do not claim it controls every local process, and do not describe a native adapter until the code and tests prove that adapter path exists.
For security-sensitive reports, use the security guide instead of opening a public issue.