This page is for developers changing Magistr itself or integrating with its implementation. To use Magistr on your own project, start with Installation and Connect an agent.
Magistr is a source preview. The repository is public; downloading its workflow artifacts needs a GitHub account.
Development
Read the repository’s contribution guide, development guide, and project instructions before changing code.
Magistr has a Rust workspace and a separate desktop workspace. The website uses Astro and MDX. Development guidance identifies the commands, prerequisites, and affected checks for each area.
Choose verification for the behavior you change. Record actual results and review interface screenshots where applicable. Foreground native input tests need explicit authorization for that run.
Architecture
The architecture overview maps component ownership and links to the detailed contracts.
Use the relevant contract before changing a shared boundary:
- Sessions covers agent sessions and their owners.
- Desktop covers the graphical application and verification limits.
- Terminal covers terminal presentation.
Product instructions live in this public manual. Repository architecture pages explain implementation responsibilities and are not a second installation guide.
Integration
The Codex reference documents launcher and skill-selection behavior for integration work.
Tool recovery covers tool errors and recovery contracts. Authentication describes the configured team-identity protocol and its verification limits.
For ordinary model choices and approval behavior, use Configuration and Permissions.
Releases and deployment
The release inventory and CLI release guide describe maintainer packaging and publication work. Release security covers release checks.
Website build and verification instructions are in the website README. These maintainer procedures do not mean a public package is already available.
Historical evidence
The repository documentation index separates current guidance from dated investigations, benchmarks, and screenshot evidence. Historical evidence describes the source and environment recorded at that time; it is not a current installation or support guarantee.
The landing page’s recorded build is an independent example. Its original records remain useful even when the current manual changes.