Agentic AI-Powered Dev Automation

Backlog to PR
in Minutes,
not Sprints.

AGENA is an agentic AI platform powered by pixel agent technology. It runs an autonomous PM → Dev → Reviewer pipeline that writes production code, reviews quality, and opens GitHub PRs with full task telemetry.

JiraAzure DevOpsGitHubOpenAI
LIVE
CLI · v1.2.0
Install, log in, and run the daemon — one command each
brew install aozyildirim/tap/agena · agena setup · device-code OAuth + auto-enrollment. No JWT copy-paste, keychain-backed auth.
npm install -g @agenaai/cli

All integrations are unified in one panel and events flow end-to-end automatically.

Azure DevOpsAzure DevOps
JiraJira
YouTrackYouTrack
GitHubGitHub
OpenAIOpenAI
GeminiGemini
SlackSlack
Microsoft TeamsMicrosoft Teams
New RelicNew Relic
SentrySentry

See The Real Flow Design Clearly

AGENA Agentic AI Pipeline Flow - Autonomous Code Generation Workflow

SeeTheRealFlowDesignClearly

This visual shows how task stages move through the agent pipeline. Each step runs with live logs and control layers.

Stage transitions are observable and auditable.
Approval gates and risk signals are visible on the flow.
Code generation and PR lifecycle are unified in one schema.

Control the whole flow from one cockpit

Patron Modu

Patron Mode combines workload, risks, and AI spend in one panel. Make fast decisions and steer the team instantly.

|

How Qdrant-based semantic memory works

During flow execution, the system retrieves similar tasks from Qdrant vector DB to strengthen prompt context. This drives more consistent, faster, and more accurate code generation inside the same repo scope.

Usage in Flow

During fetch_context, similar records are retrieved and injected into analyze/generate/review stages.

Task title + description is transformed into an embedding query.
Tenant-scoped similar records are searched with organization_id filter.
Top matches are summarized into context summary.
After finalize, new output is written back as memory.

Stored Fields

Primary fields stored in Qdrant payload:

keyTask tracking key for traceability.
organization_idUsed as tenant isolation filter during retrieval.
inputSnapshot of task title + effective description.
outputSnapshot of finalized generated code output.

Embedding Scope

Content types currently matched through memory:

01Task title + description (query side)
02Task title + effective prompt context (write side)
03Finalized generated code output (write side)
04Context summary enriched by repo/tenant rules

Story Points grounded on your team's history

The LLM pulls your team's closed work items (final SP + assignee + PR titles + branches) from a vector index and anchors every new estimate on the closest matches — by name. No generic estimates, your velocity and your patterns.

01

Backfill History

One click pulls every closed, SP-assigned item from Azure DevOps / Jira into Qdrant. Each is embedded with title + description + branch names + PR titles.

02

Find Neighbors

The new item is queried as a vector; hits below cosine 0.55 are dropped. Top-5 survivors are returned, with same-type items (Bug/Story/Task) preferred when possible.

03

Inject into the Prompt

Each hit goes into the LLM prompt with its SP badge, similarity %, previous assignee and linked PR titles. The model reasons "closest is #X, Ali did it at 3 SP."

04

Explained Suggestion

SP badge + confidence + rationale naming the prior items it's based on + a paste-ready comment. One click writes it back to Azure / Jira.

💡Example: "#62840 (Ali, 5 SP) and #61206 (Ayşe, 3 SP) are closest. Auth cache invalidation, closer to #62840 — suggesting 5 SP."

Your team's solutions compound

Every completed task turns into a reusable skill: approach, prompt fragment, touched files, tags — all in a vector index. When a new task arrives, the closest skills are prepended to the agent's system prompt. Your team never discovers the same solution twice.

01

Task Completes

Agent writes code, opens the PR, task marks completed. A fire-and-forget job kicks the Skill Librarian.

02

LLM Distils the Pattern

OpenAI / Claude CLI / Codex CLI summarises title + description + reviewed code into { name, approach_summary, prompt_fragment, tags }. Skipped when confidence < 50 so too-unique tasks don't pollute the catalog.

03

Indexed to Qdrant

Upsert with kind='skill' payload, org-scoped, distinct from refinement history. A DB row is created too, powering the catalog UI with usage counters.

04

Injected into Future Prompts

Before the agent runs, top-3 skills above the relevance threshold are retrieved and prepended to the system prompt as a RELEVANT TEAM SKILLS block. Works in Claude CLI, Codex CLI, classic pipeline — all four modes.

📋

Yesterday's task

#61981 — Color variant link routes to wrong product. Senior dev fixes it by adding a fallback in ColorVariantResolver and tightening the slug regex.

🧠

Skill auto-extracted

name: Color-variant routing fallback · tags: routing, slug, e-commerce · approach: route through ColorVariantResolver, never inline the slug parse.

Today's task

#64044 — Category filter loses variant on pagination. Top skill match (81%) is the routing fallback above. Its prompt fragment is injected: agent skips inline slug parse, reuses the resolver, ships a fix consistent with the team's precedent.

🧠Result: after ~50 tasks, the catalog carries 20+ team-specific patterns ("Use ArrayHelper::safeGet on our webservice", "Order endpoints go through the OrderContext factory"). New devs or agents learn your codebase's conventions in minutes, not weeks.

Compute everywhere — one dashboard

Your laptop, your teammate's machine, a cloud daemon — each registers as a Runtime. Token-based enrollment, 30s heartbeat, live status. Assign a task to a specific runtime (routing ships next).

01

Bridge starts

bridge-server.mjs reads AGENA_JWT + AGENA_TENANT_SLUG. Absent → prior behaviour. Present → proceeds to enrollment.

02

Enroll + token

POST /runtimes/register with name, platform, discovered CLIs (claude/codex). Backend mints a one-shot token, stores only a sha-256 hash, bridge persists to ~/.agena/runtime.json.

03

30s heartbeat

Heartbeat every 30s with X-Runtime-Token, refreshing CLI list + daemon version. UI polls every 10s; status dot (green/grey/red) is live.

04

Routing (next up)

GET /runtimes/{id}/tasks/next is already stubbed. Daemons will poll it for work; you'll be able to pin a task to a specific runtime from the UI.

💻Example: three teammates, each running the bridge on their mac. Three green runtimes in the dashboard. Fire a heavy test at Ali's machine while yours is busy — no build-env contention.

Blocked items, gently unblocked

Every blocked Azure / Jira ticket in the sprint gets a Ping button. Agena reads the thread, checks the last reply, and if it's been silent for 24h, an LLM drafts a short polite status-check — in the target language, signed by Agena — and posts it back with an @mention. 48h cooldown + DB-persisted history, so nobody ever gets pinged twice.

01

Last-reply radar

Fetches the comment thread from Azure DevOps or Jira and measures hours-since-last-activity. Anything <24h old is skipped — no noise.

02

AI writes, you choose

Pick the LLM at send time: Claude CLI + sonnet (via the host bridge), Codex CLI, OpenAI, Gemini, or HAL. Claude failures auto-fall-back to Codex on the same bridge.

03

Localized, tagged, signed

Message is generated in the chosen language (7 locales), wrapped with <at>@Display Name</at> so Azure renders a real mention, and signed "written by Agena via {model}" for full transparency.

04

Cooldown + history

Every successful nudge is stored in nudge_history. The UI badges already-pinged items with "Agena pinged Xh ago" and a 48h cooldown blocks accidental spam.

🤖@Ali No progress for 45 hours on the new node type for Agena Flow Editor — can you share a quick status? — 🤖 Agena via claude_cli · sonnet

Drive Agena from the terminal

Install once (brew or npm), log in with device-code OAuth, and get every dashboard workflow — tasks, skills, sprint refinement, runtimes — as a single-binary command. JWT held in the OS keychain; no copy-paste.

01

Auth + tenant

agena login opens a browser for RFC 8628 device-code, stores the JWT in macOS Keychain / libsecret / Windows Credential Manager. Switch orgs with agena org switch <slug>.

02

Tasks

agena task create -t "Fix login" --assign enqueues for the AI agent; task list / show / logs give you the full trail without opening the dashboard.

03

Skill catalog

agena skill search "nullable pointer" vector-matches the team's auto-extracted patterns; list / show / delete round out the catalog.

04

Sprint refinement

agena refinement backfill indexes your Azure/Jira history into Qdrant. agena refinement analyze gives grounded SP estimates before the planning call.

$ brew install aozyildirim/tap/agena $ agena setup # device-code OAuth + enrolls this machine $ agena task list $ agena skill search "nullable pointer panic" $ agena refinement analyze -p MyProject -t MyTeam
💻Install: brew install aozyildirim/tap/agena · or npm install -g @agenaai/cli. The bridge is bundled — agena daemon start just works.
0%
PR Success Rate
0x
Faster Delivery
0+
Teams Onboarded
0M+
Tasks Automated

Everything your team needs to ship faster

🔐
Multi-Tenant Security

JWT auth, org-level isolation, usage limits, and billing controls baked in from day one.

🤖
Agentic AI Delivery Flow

Pixel agent architecture with LangGraph state machine providing full observability across each AI stage of your pipeline.

GitHub Automation

Branch, commit, and PR generation with traceable task links and review summaries.

💰
Cost Optimized LLM

Prompt caching, model routing, and token/cost tracking per organization.

🔀
Multi-Repo Orchestration

One task, multiple repos — AGENA runs parallel agent pipelines and creates separate PRs for each repository.

🔗
Shareable Tasks

One-click tokenised links carry the description, comments and screenshots. Recipients import into their own org with a single button — WhatsApp, Teams and Slack share targets included.

Two production workflows that pay rent every day

Two of AGENA's flagship automations live here: stale-ticket triage that scans Jira & Azure DevOps directly at the source, and a review-backlog killer that nudges humans before code rots. Both are fully org-scoped, multi-channel, and AI-powered — no env keys, no mock outputs, just the agent your team configured.

🧠CROSS-SOURCE INSIGHTS

Which deploy caused this bug — answered in 5 seconds

Correlates PR merges, deploys, Sentry / NewRelic / Datadog / AppDynamics errors and Jira / Azure DevOps work items into confidence-scored clusters. One timeline, one narrative, one click to rollback.

  • Confidence-scored clusters (0-100)
  • Sentry / NewRelic / Datadog / AppDynamics + Jira / Azure
  • Auto-rollback PR with one click
  • Polls every 5 minutes — cheap DB reads
See it in action
🧹STALE TICKET TRIAGE

Source-side scan. AI verdicts. One click apply.

Scans Jira (search/jql) + Azure DevOps WIQL across every project, asks your reviewer agent (Claude / Codex / OpenAI) for a verdict on each idle ticket, and lets you bulk-resolve in one modal. Cancelled / Won't Fix excluded by default; project + state + source filters baked in.

  • Background scan with live progress — UI never blocks
  • source_updated_at cache skips re-LLM on unchanged tickets
  • Configurable look-back window (e.g. last 12 months only)
  • Verdicts use your org's CLI — claude_cli, codex_cli, or hosted OpenAI
See it in action
REVIEW BACKLOG KILLER

PRs gathering dust? Nudge across 5 channels with the right tone.

Tracks every open PR's age, posts a polite nudge to Slack DM / WhatsApp / email / Telegram / the PR comment thread itself — in 7 languages, optionally AI-generated by your reviewer agent reading the actual diff. Built-in 24h floor, deletion detection, and per-row cooldown so nobody gets spammed.

  • Multi-channel: Slack DM, WhatsApp, email, Telegram, PR comment
  • AI body that reads the diff and asks specific questions
  • Auto-nudge worker (opt-in) with 24h interval floor
  • Searchbox + chip-tag exempt-repo picker — never spam infra repos
See it in action
🗄Workspaces

One platform, a workspace per squad

Big eng orgs split into Backend / Mobile / Payments — each scope gets its own tasks, repos, AI agents and 6-character invite code.

  • Per-squad task pools, repos, AI agents
  • 6-character invite codes (no SCIM)
  • Per-workspace titles ('Tech Lead', 'QA')
  • Org-owner cross-workspace dashboard
See it in action

Multi-Repository Orchestration

Assign a single task to multiple repositories simultaneously. Each repo gets its own AI pipeline execution and pull request.

🎯One task triggers independent pipelines across all linked repositories
Parallel execution — each repo runs its own AI agents simultaneously
🔒Per-repo locking prevents conflicts between concurrent operations
📊Unified dashboard shows all PRs and their status in one view
Task #142Fix auth flow
↓ fan-out
backend-api
fix/auth-jwt
✓ PR #87
frontend-app
fix/auth-ui
✓ PR #214
shared-types
fix/auth-types
⟳ running
2/3 completed
Task Dependency Pipeline
#31DB Migration
done
#32Backend API Update
done
#33Frontend Update
running
#34E2E Tests
waiting
Auto-queue: #33 auto-queued after dependencies completed

Chain Tasks. Automate the Sequence.

Define execution order between tasks. When a dependency completes, the next task in the chain starts automatically — no manual intervention needed.

🔗Set dependencies at task creation or anytime after
Auto-queue: dependent tasks start when blockers complete
🛡️Cycle detection prevents circular dependency chains
📈Visual dependency flow shows the full execution pipeline
Learn More

Three steps to autonomous delivery

01

Ingest

Pull work from Jira/Azure or create directly in the dashboard. AI parses intent and context.

02

Orchestrate

PM, Dev, and Reviewer agents collaborate through LangGraph states with full telemetry.

03

Ship

Reviewed output becomes a GitHub PR with timeline, logs, and quality scores.

See it in action

📋

Live Task Board

Track queued, running, and completed tasks with per-task AI timeline and cost breakdown.

🎯

AI Assignment

One click "Assign to AI" with Azure/Jira import actions inside the dashboard.

Watch flow and agent engine in real time

Track flow orchestration and role-based agent behavior in a single view.

Flow
LIVE

Flow Intelligence

See node-graph stages, approval gates, and execution chain in real time.

Active Nodes12
Approval Gates3
Avg Runtime2m 14s
Context fetch
Spec planning
Code + review
PR finalize
🤖 Agents
Live synchronization

Agent Team

Monitor model, specialization level, and pipeline contribution for each role with a live distribution.

PM Agentgpt-4o
Developer Agentgpt-4o-mini
Reviewer Agentgpt-4.1
Task Share

Production-grade AI delivery engine capabilities

Make AI delivery safer, governed, and predictable with dependency graph, PR risk scoring, and tenant playbook controls.

🧩 LIVE4 Nodes · 2 Approval Gates

Task Dependency Graph

Connect tasks, surface blockers, and automatically prevent assignment before prerequisite work is completed.

INTAKEDEVREVIEW
Cycle GuardBlocker VisibilitySmart Queue
72
HIGH RISK

PR Risk Scoring

Generate a live risk score per task using file churn, critical-path touches, and diff scale.

Tenant Playbooks

$ run tests before push
$ keep methods unchanged
$ minimal patch only
Org RulesPrompt Injection

Task Story Mode

Agents interpret intent more accurately with business context, acceptance criteria, and edge-case notes.

Context
Acceptance
Edge Cases

Cost Guardrails

Prevent budget overrun with per-task token/cost limits, then auto-stop or request approval at threshold.

Context fetch
Spec planning
Code + review
PR finalize

New Relic + Sentry Errors → AI-Fixed PRs

Auto-detect production issues from New Relic APM and Sentry, create fix tasks, and let AI agents resolve them with pull requests — hands-free.

📊

Auto Error Import

Connect your New Relic account and automatically import error groups from APM entities. Deduplication prevents duplicate tasks.

🔍

Smart Error Parsing

Extracts file paths, line numbers, and affected endpoints from error messages. Agents know exactly where to fix.

🔗

Entity-Repo Mapping

Map New Relic entities to your repositories. When errors are imported, the system knows which codebase to target.

🔄

Scheduled Polling

Enable auto-import per entity. The worker polls New Relic every 5 minutes and creates tasks for new errors automatically.

📊
Flow Integration
Use the New Relic node in visual flows to fetch errors, filter by conditions, and trigger AI agents to generate fixes.
Trigger → New Relic → Condition → Developer → PR
🚨
Sentry Issue Flow
Stream Sentry issues into your fix pipeline, apply triage conditions, and let AI agents generate patch PRs automatically.
Trigger → Sentry → Condition → Developer → PR

Real-time delivery visibility with Slack and Teams

With Notification Router, pipeline events, PR outcomes, failure signals, and approval steps are automatically routed to the right channel.

Slack
Slack Delivery
Notification Router

Task state transitions, PR creation events, and failed run alerts are sent instantly to the selected channel.

Microsoft Teams
Teams Delivery
Approval + Delivery Feed

For enterprise teams, pending approvals, cost/limit warnings, and result summaries are published into Teams feed.

Single notification service, multi-channel dispatch
Event-type based routing rules
Task/PR contextual message payloads
Per-profile channel on/off control

Recently shipped platform capabilities

Live streaming, safer code generation, and clearer task visibility are now showcased with animated cards on the landing page.

🟢LIVE

Live Task Log Stream

Task detail now streams logs in real-time via SSE; follow stage updates without refreshing.

🧠LIVE

Repo-Stack Safe Generation

Agents now stay aligned with repository stack; absolute-path and stack-drift outputs are filtered at backend level.

🧭LIVE

Accurate Step Progress

Execution progress is computed with stage aliases, reducing false pending states in the UI.

📊LIVE

Transparent Usage Signals

Task duration, token, cost, and run telemetry are now easier to track in the interface.

Loved by developers

AGENA turned our 2-week sprint into a 2-day sprint. The AI agents generate production-ready PRs that actually pass code review.

AM
Alex M.
Senior Developer

The flow builder is incredible. We automated our entire PR pipeline — from Jira ticket to merged code — with zero manual intervention.

SK
Sarah K.
Engineering Lead

As a small team, AGENA is like having 3 extra senior developers. The code quality from the AI review pipeline surprised us.

MY
Mehmet Y.
CTO, Startup

GitHub and Azure DevOps integration works flawlessly. We process 50+ automated PRs per week with AGENA agents.

DR
David R.
DevOps Engineer

I write task descriptions and AGENA delivers working code. It changed how our entire team thinks about product delivery.

LC
Lina C.
Product Manager

The pixel agent visualization makes AI workflows transparent. I can see exactly what each agent is doing in real-time.

KT
Kenji T.
Full Stack Developer

Frequently Asked Questions

What is AGENA?+

AGENA is an agentic AI platform that autonomously generates code, reviews quality, and creates pull requests. It runs a PM → Developer → Reviewer → Finalizer pipeline powered by pixel agent technology, turning your backlog into production-ready PRs in minutes.

What is agentic AI?+

Agentic AI refers to AI systems that can autonomously plan, execute, and adapt to achieve complex goals. Unlike simple AI assistants, agentic AI agents work independently through multi-step workflows — analyzing tasks, generating code, reviewing quality, and shipping features without constant human guidance.

What is pixel agent technology?+

Pixel agent technology is AGENA's visual orchestration layer that represents each AI agent as an interactive pixel character. It provides real-time visibility into your autonomous AI workforce — showing which agents are active, what they're working on, and the progress of each task through the pipeline.

Which platforms does AGENA integrate with?+

AGENA integrates with GitHub and Azure DevOps for PR automation, Jira for task import, Slack and Microsoft Teams for ChatOps notifications, and supports OpenAI and Google Gemini as LLM providers.

Is AGENA free to use?+

Yes! AGENA offers a free tier with 5 tasks per month, token usage tracking, and community support. The Pro plan ($49/month) includes unlimited tasks, priority worker throughput, team invites, and billing via Stripe or Iyzico.

Is AGENA open source?+

Yes, AGENA is fully open source under the MIT license. You can self-host it or use the managed platform. The source code is available on GitHub at github.com/aozyildirim/Agena.

GlossaryIntegrationsUse CasesCompare
Ready to ship?

Build Faster.
Review Better. Ship Safer.

Create your workspace and run your first autonomous delivery cycle today.

Launch AGENA - It's Free