Seer suggests fixes inside Sentry.
AGENA actually opens the pull request.
Open-source, self-hostable, BYO LLM key. Same Sentry-to-fix loop, but it ends with a merged PR on GitHub or Azure DevOps and an auto-resolved Sentry issue — not an inline suggestion.
Frequently asked
Is AGENA a Sentry replacement?
No — AGENA does not capture or store errors. You keep using Sentry as your error monitor; AGENA reads Sentry issues via API and turns them into pull requests. Think of AGENA as the layer that takes a Sentry issue and ships a fix.
Why not just use Seer?
Seer is great for inline fix suggestions, but the loop ends inside Sentry. AGENA closes the loop end-to-end: imports the issue, runs an OWASP-aware reviewer, opens the PR, posts a comment back on Sentry, and resolves the Sentry issue when the PR merges. The cycle from alert to merged PR runs in 8–15 minutes with zero human keystrokes.
Can I use both?
Yes — they are complementary. We surface Seer’s fixability score on each Sentry issue card so you can scan which issues to auto-fix vs. flag for human review. Seer’s in-Sentry suggestions still work for cases where AGENA isn’t involved.
Does AGENA need access to my source code?
Only the diff and ±5 lines of context for the file:line in the stack trace. You can self-host AGENA fully air-gapped — the only network egress is to Sentry, your VCS, and your chosen LLM provider.