Question 1

Does Blue Mantis merge code?

Accepted Answer

No. It creates a branch named task/<id>, commits the suggestion you chose, and opens a pull request. Merging stays with your review rules and your CI.

Question 2

How are credentials handled?

Accepted Answer

Tracker credentials (Jira, Azure DevOps) and repository credentials (GitHub, Azure Repos) are stored against your user, tested when you save them, and never written to a log line. Agent infrastructure is managed by Blue Mantis — no model API keys required from you.

Question 3

How much of my repository do the agents see?

Accepted Answer

The files the keyword extractor selects as relevant to the work item, plus the detected stack profile. Not the whole tree, and nothing outside the repository you bound to the project.

Question 4

What happens if a scheduled run fails?

Accepted Answer

The run row records the error, the item is left untouched, and the owner gets an email. Runs stuck longer than twenty minutes are swept to failed by the dispatcher.

Question 5

Can it write to my tracker?

Accepted Answer

Only where you ask it to: new items and test cases you explicitly push, and a status change when an item closes. Nothing else propagates upstream.

Question 6

Which providers work best?

Accepted Answer

GitHub is the primary, auto-synced provider. Azure Repos works for edits to existing files; adding a brand-new file can fail there.

Question 7

Six agents — why so many?

Accepted Answer

Each agent has a distinct role. Raptia and Fovea generate competing suggestions in parallel — they reason differently by design, so when one misreads the ticket, the other usually does not. Synthesia scores both on five dimensions and recommends the stronger answer with a confidence score. Veria reviews the committed code against the acceptance criteria after commit. Aegis scans for security vulnerabilities and blocks High findings from reaching main. Narratia writes the operational runbook. Together they cover the full delivery loop from generation to documentation.

Question 8

What does Aegis scan for?

Accepted Answer

Aegis checks for OWASP Top 10 (2021) vulnerabilities: injection flaws (SQL, NoSQL, command), broken access control, cryptographic failures, hardcoded secrets, insecure design, authentication bypasses, and SSRF. Each finding has a severity (Critical, High, Medium, Low, Info), an OWASP category, a line reference, and a remediation step. High and Critical findings block the PR. Medium and Low findings create tracker tickets.

Question 9

Can Blue Mantis fix its own security findings?

Accepted Answer

Yes — that is what Remediate Now is for. Click it on any Aegis finding and Blue Mantis creates the tracker ticket, syncs it to the board, and immediately starts a new run with the security finding and its remediation as the brief for Raptia and Fovea. The loop closes in the same session without switching tools.

Question 10

What does Narratia put in the runbook?

Accepted Answer

Seven sections: a summary of what changed and why, deployment steps specific to this change, a rollback procedure referencing the branch and PR, validation commands to confirm it is working in production, the generated test cases, security findings from Aegis, and a references section with the work item key, branch, commit hash, and PR link. Pushed to Confluence, Notion, or committed as Markdown to the same PR branch.

Question 11

Can I try it on one project?

Accepted Answer

That is how every pilot starts: one tracker project, one repository, one real work item run end to end on a shared call.

The questions
engineers ask first.

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

Queue the work tonight.Read the pull requestsin the morning.

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