Developer docs
For people building on Moguri's SDK or contributing to Moguri itself: architecture, the shared SDK and CLI, local setup, checks, releases and contribution rules.
How Moguri is built
The desktop app, terminal UI and CLI are clients of one local service, and they all use the same importable SDK. The service records everything as an append-only, versioned event stream in an encrypted SQLite store and migrates it forward on upgrade. Model calls and tools run in supervised workers the service can cancel.
- TypeScript on Node.js 26, with Electron and React for the desktop app and OpenTUI for the terminal UI.
- One service writer and one shared typed command protocol. Commands carry idempotency IDs, and editable data carries revision checks.
- Clients can't approve on a model's behalf, silently substitute a model or backend, or reset accounting.
Read the architecture overview for the contracts, and the implementation specification for the target product.
Start
Development setup lists the toolchain and every check, from npm run typecheck to the hidden Electron end-to-end suite. CI runs only after merging to main, so contributors run the relevant checks locally before opening a pull request.
Architecture and API
Project
Source code
Moguri is MIT-licensed, but its source repository isn't public yet. Until it is, links to it would return 404, so this site doesn't link to it. Pages marked as published from the source repository are exact copies of its documentation at commit b686ddc.
- Report security issues privately to security@mb-consulting.dev, as the security policy describes.
- Follow Moguri on GitHub for the public repository and releases.
- The website itself is public: moguri-dev/moguri.synctune.it.