The AI Architect for your codebase.
Hyrax maps how the repository works, evaluates it across six dimensions of product-grade engineering excellence, and delivers verified upgrades through GitHub. Developers review and merge every change.
One architectural context, from anatomy to pull request
Each stage hands to the next. Discovery builds the context, agents apply judgment across six dimensions, work is prioritized P0 to P3, and verified upgrades return through GitHub.
Map
Repository anatomy and architectural context
Discovery maps services, dependencies, conventions, and boundaries, then writes the context to HYRAX.md and .hyrax/discovery.
See it 02Prioritize
Six dimensions, one ranked list
Specialized agents evaluate the codebase across six dimensions of excellence. Each result carries a P0 to P3 priority with file and line.
See it 03Deliver
Verified pull requests through GitHub
Each change passes the 13-step verification gate before it becomes a pull request. Developers review and merge.
See it 04Learn
More context with every cycle
Hyrax reviews each push against the architectural context, and accepted changes feed the next cycle.
See itHyrax maps repository anatomy
Hyrax clones the repository into isolated compute and maps services, dependencies, conventions, boundaries, and risks. Specialized agents then reason across security, correctness, maintainability, performance, architecture, and operations.
Prioritize what matters
Hyrax turns architectural and codebase judgment into prioritized work. P0 items lead the queue, and architectural guidance sits apart from them with stable references.
Verified changes arrive as pull requests
Hyrax writes the change in an isolated worktree, runs the tests and build, and passes the 13-step verification gate before it opens a pull request. Required checks stop the run if they fail.
Every cycle adds codebase context
Hyrax reviews each push against the architectural context and returns a clear verdict. Accepted changes become deterministic patterns, so each cycle gives Hyrax more context.
Code review is one workflow surface, not the category.
Static scanners, AI code review, and dependency tools can stay in place. Hyrax runs alongside them and returns verified upgrades as pull requests.
Static scanners
Match known patterns on every push
- Flag, never resolve -- output is a queue
- No sense of your conventions
- False positives are yours to triage
AI code review
Triage, explain, and judge changes
- Built around changes someone else made
- Suggestions ride the review thread
- Codebase monitoring is security-only
Dependency security
Track CVEs in your packages
- Blind to your first-party code
- Version bumps, not code changes
- Alerts scale faster than changes
Hyrax
From issue to merged change
- Reads the codebase continuously
- Surfaces issues before PRs exist
- Changes in the repo's conventions
- Baselines tests, runs the suite
- Ships the PR merge-ready
- Closes ticket on merge
An engineer reviews and merges. That never changes.