Contribute
Contributing
Change AgentOS through its ownership boundaries and evidence-driven review path.
AgentOS welcomes generally useful improvements upstream while keeping organization-specific
behavior in the owning fork or private configuration. Begin with the root and nearest
AGENTS.md, then use the development Skill for every AgentOS source change.
Repository map
Find the smallest component that owns the behavior you need to change.
Development workflow
Use the reviewed Bun/Mise workspace, isolate changes and deliver through review.
Testing and verification
Prove behavior through public interfaces before describing a change as complete.
Evaluate an organization
Freeze sanitized evidence against the public AgentOS benchmark before improving it.
Improve from evidence
Turn one frozen failure into the smallest reviewed and regression-tested change.
Release model
Build immutable artifacts from a clean exact revision and publish only after verification.
Last updated on