Blue Mantis
Sign inRequest access

Your tracker.
Your repository. Your keys.

Blue Mantis stores every credential against your user record, tests it before it's saved, and tells you plainly what each one can reach.

JiraTRACKER

Syncs the epic→story→task hierarchy into a board, resolves parents in two passes, and writes new items and test cases back when you ask it to.

JIRA_DOMAIN · JIRA_EMAIL · JIRA_API_TOKEN
Uses the enhanced JQL search endpoint; your domain is normalised for you.
Azure DevOpsTRACKER

The same sync against Azure Boards, with Feature mapped onto epic so the hierarchy lines up with Jira projects.

AZURE_DEVOPS_ORG · AZURE_DEVOPS_PROJECT · AZURE_DEVOPS_PAT
Work-item creation and test-case push both supported.
GitHubPRIMARY REPO

Branch, commit and pull request. Stack detection reads the repository on connect, and the test-script commit stacks onto the existing PR rather than overwriting it.

GITHUB_TOKEN (PAT) or the OAuth token from sign-in
The primary provider, and the one we test first on every release.
Azure ReposREPO

Commits and pull requests against an existing file tree, for teams whose code lives beside their boards.

AZURE_REPOS_ORG · AZURE_REPOS_TOKEN
Edits to existing files are reliable; brand-new file adds can fail.
RaptiaAGENT

The first of two generation agents that runs on every Blue Mantis pipeline. Raptia is optimised for precision — it reads the work item, the acceptance criteria, and the repository context, then commits to a single well-reasoned answer. Stack-aware: detects React, Angular, Vue, Node.js, .NET, Java Spring Boot, Python, and Go — and writes idiomatic code for each without being told.

Configured by Blue Mantis — no separate credential required
Raptia and Fovea always run together in parallel.
FoveaAGENT

The second generation agent. Fovea takes a wider view of the same context — it considers more of the repository before settling on an approach, which means it often catches what Raptia misses. Also stack-aware — uses the same detected profile to ensure both suggestions follow the same framework conventions.

Configured by Blue Mantis — no separate credential required
The Synthesia agent scores both and flags the stronger answer.
SynthesiaAGENT

The ranking agent. After Raptia and Fovea complete, Synthesia scores both suggestions on correctness, readability, diff size, convention adherence, and acceptance-criteria coverage — then recommends the better one with a confidence score. Two behaviour signals — ambiguity handling and surgical precision — flag whether an agent silently assumed something or changed more than the work item required.

Runs automatically after every generation — no configuration needed
Synthesia's verdict is visible on every run. You can always override it.
VeriaAGENT

The review agent. After you commit a suggestion, Veria reads the committed code against the work item's acceptance criteria and produces a structured review: strengths, gaps, risks, and a one-sentence focus note for the human reviewer.

User-triggered post-commit — runs on demand, not automatically
Veria only activates after a suggestion is committed to a branch. Veria explicitly checks for scope creep, silent assumptions, and over-engineering in the committed code.
AegisAGENT

The security agent. Runs after commit using a frontier security model. Scans the committed change for OWASP Top 10 vulnerabilities, hardcoded secrets, injection flaws, and authentication bypasses. Outputs structured findings with severity, OWASP category, line reference, and remediation steps. High and Critical findings block the PR via a GitHub status check. Remediate Now creates a tracker ticket, syncs the board, and starts a new run to fix the issue — without leaving Blue Mantis.

Configured automatically — no separate credential required
Aegis uses claude-fable-5, the safeguarded frontier model. Configure GitHub branch protection once to enforce the stop gate.
NarratiaAGENT

The documentation agent. After a run completes, Narratia generates an operational runbook: a summary of what changed, deployment steps specific to this change, rollback procedure, validation commands, test cases from the generated suite, and security findings from Aegis. Pushed to Confluence, Notion, or committed as Markdown to the PR branch.

Confluence: CONFLUENCE_DOMAIN · CONFLUENCE_EMAIL · CONFLUENCE_API_TOKEN · CONFLUENCE_SPACE_KEY Notion: NOTION_API_TOKEN · NOTION_PARENT_PAGE Markdown: no credentials required
The Markdown option commits docs/runbooks/ITEM-KEY.md directly to the PR branch — visible in the PR with no extra setup.

Capability matrix

CapabilityJiraAzure DevOpsGitHubAzure Repos
Read hierarchyYesYes
Create work itemsYesYes
Push test casesYesYes
Status write-backOn closeOn close
Branch and commitYesExisting files
Open pull requestYesYes
Stack detectionYesYes
Security gate (stop gate)Yes
Runbook pushMarkdown to PRMarkdown to PR

GitHub is the primary, auto-synced provider. On Azure Repos, commits edit existing files — adding a brand-new file can fail.

Request access

Queue the work tonight.
Read the pull requests
in the morning.

Request accessRead the guides