The backlog
writes the code
back to you.
Blue Mantis reads a work item the way an engineer does — hierarchy, acceptance criteria, the repository it belongs to — then runs four agents against it — Raptia and Fovea generate competing suggestions, Synthesia ranks them, and the pull request opens. Run it now, or queue tonight's work and read the diffs in the morning.
No agent runs without your credentials, and none of them leave your repository.
Try the loop
Live demo — click through with sample dataPick a work item, run the agents, commit the suggestion you want. Nothing here is a screenshot.
Seven steps, one thread
From the credential you paste on day one to the test case that lands back in Jira, every step is scoped to your account and your repository.
Where it plugs in
| System | What Blue Mantis does |
|---|---|
| Jira | Syncs the epic→story→task hierarchy into a board and writes items and test cases back on request. |
| Azure DevOps | The same sync against Azure Boards, with Feature mapped onto epic. |
| GitHub | Branch, commit and pull request, with stack detection on connect. The primary provider. |
| Azure Repos | Commits and pull requests against an existing file tree. |
| Raptia · Fovea · Synthesia · Veria · Aegis · Narratia | Six agents, one pipeline per run |
What we don't do
We don’t hold shared credentials. Every key is stored against your user record and tested the moment you save it. No pooled key, no environment fallback in production.
We don’t merge anything. Blue Mantis opens the pull request. Your review rules and your CI decide whether it lands.
We don’t rewrite your board. Items and test cases go upstream only when you ask. The single automatic write-back is a status change when an item closes.
We don’t guess your stack. Stack detection reads the bound repository so the agents write your framework, not generic pseudocode.