Omega

When	Who	Action	Details

Deploy frequency (PRs merged/week)

Stacked: Omega-authored PRs vs human-authored. Requires REPO_URL set.

Lead time for changes (hours)

Time from PR open to merge. Median (solid line) and p90 (dashed line). Approximates lead time using PR createdAt as the start anchor — the exact DORA definition is first-commit→merge, but fetching every PR's commit history blew GitHub GraphQL's node limit on large monorepos. Slightly underestimates lead time for branches with significant pre-PR work, but tracks the same trends.

Feature funnel (weekly cohort)

Outcome of features that terminated this week (completed / failed) plus in-flight features bucketed by creation week. Rejected is a per-event count (each plan rejection in the week), not a feature outcome — a feature can be rejected once, replanned, and still ship as completed.

Cycle time decomposition (median hours)

Where time goes inside a shipped feature (Omega-completed with a PR opened): planning, implementation, and code review. Per-task completions without a PR are excluded.

First-pass rates (%)

Pre-push review, code review, and CI passing on the first try. Each series has its own denominator: pre-push counts shipped features where pre-push was actually reached (prePushReviewAttempts > 0); code-review and CI count shipped features with the corresponding lifetime counter (pre-OMG-100 rows are excluded); CI further requires ciStatus.state === 'pass' && ciStatus.total > 0 so features that bypassed the CI gate (no checks configured, status fetch failure) aren't counted as first-pass successes. Higher is better.

Retries per shipped feature

Copilot code-review fix iterations (from lifetimeCodeReviewFixAttempts) plus rejected → planning transitions. Median + p90. Features that shipped before OMG-100's instrumentation landed do not have the lifetime counter, so their code-review-fix component contributes 0 — older buckets undercount real retries.

Cost per shipped feature (USD)

Total Claude spend per Omega-completed feature with a PR opened: plan + refine + implementation + acceptance + pre-push + code-review + CI-fix. "Shipped" means Omega finished its work and opened a PR — the human merge button is independent of this signal; "deploy frequency" is the only chart on this page that gates on actual merge. Pre-OMG-100 rows lack lifetimeCiFixCost and contribute 0 for the CI-fix component, so older buckets underreport actual spend.

Select a feature to view agent activity

Real-time agent output streams here

GitHub access

Choose how Omega authenticates with GitHub for repository reads and pull-request creation.

Authentication method

App ID

Installation ID

Private key

Default repository URL

Used when a feature does not specify its own repository.

Ticket tracker

Link features to an external project tracker so engineering, product, and program management stay in sync.

Provider

Notion integration

When set, Omega resolves Notion links found in Linear ticket bodies and comments at submission time and injects the page contents into the planner prompt.

Notion integration token

Create an internal integration at notion.so/profile/integrations. Each Notion page that should be readable must be shared with this integration (Share → Connections). Rotate by pasting a new value and saving — the runtime validates against the Notion API and re-enables resolution on this task only if validation succeeds; an invalid token persists but leaves Notion resolution disabled (in production, search CloudWatch for log entries with component: "config" and message starting with "Notion integration: disabled —" to see the validation reason). For multi-task deployments, perform an ECS service rollout after a successful rotation so the new value propagates to all tasks. To permanently disable Notion resolution in a Secrets-Manager-backed deployment, remove the integration from the Terraform-managed task definition (don't delete the AWS secret directly — that creates drift and can prevent future task starts).

Slack notifications

When set, Omega posts a Slack message on key feature state transitions (plan ready for review, agents working, feature complete, feature failed).

Incoming webhook URL

Create an incoming webhook at api.slack.com/apps (Features → Incoming Webhooks → Add New Webhook to Workspace). The URL embeds a secret path token; anyone holding it can post into the channel. Rotate by pasting a new value and saving — the runtime probes the URL against Slack and re-enables notifications on this task only if the probe passes; an invalid URL persists but leaves Slack notifications disabled (in production, search CloudWatch for log entries with component: "config" and message starting with "Slack notifications: disabled —" to see the probe reason). For multi-task deployments, perform an ECS service rollout after a successful rotation so the new value propagates to all tasks.

Single sign-on

Google Workspace SSO is the recommended way to authenticate users in production deployments.

Google client ID

Google client secret

Restrict to domain

Only emails from this domain can sign in. Leave blank to allow any Google account.

Fallback password

A shared password is always available as a backup login method.

Password

Personal access tokens

Used by MCP clients and API integrations. Set OMEGA_TOKEN in the client config.

Token name

Copy this token now — it won't be shown again.

Audit log

DORA metrics (live)

Deploy frequency (PRs merged/week)

Lead time for changes (hours)

Feature funnel (weekly cohort)

Cycle time decomposition (median hours)

First-pass rates (%)

Retries per shipped feature

Cost per shipped feature (USD)

DORA metrics

Uptime (%)

MTTR (minutes)

Deploy frequency (deploys/day)

Median PR cycle time (days)

% time on stability/scalability

In-flight diffs

GitHub access

Model provider