Help / Red Codens

Red Codens setup

Error detection to auto-fix PR. Analyzes bugs from Sentry or manual reports, generates fix plans, and submits complex fixes to the Purple chain for a PR.

Overview

Red's primary unit is the bug report. A bug report can come from any of the following:

Sentry webhook: Sentry's Internal Integration auto-files bug reports.
Manual entry (UI / API / MCP): humans or agents file bugs directly.
Blue / Purple integrations: failed E2E tests or workflow runs become bug reports.

Once analyzed, a fix plan is produced. One click (or one call) submits it to Purple Codens for a PR. A 3-Retry loop auto-improves the patch up to a few times if tests fail.

Prerequisites

A Codens account and organization.
codens-mcp installed and logged in.
Admin / write access on the target GitHub repository.
Codens GitHub App installed (required for PR creation).
For Sentry integration: Sentry organization owner / manager (required to create webhooks).

Step 1. Create a project & link a repo

Use the dashboard (app.red.codens.ai) → "New Project", or register the same repo across products via MCP:

await tools.codens_register_project_unified({
  repo_full_name: "Corevice/your-repo",
  products: ["red", "purple"]
});

During project creation, the GitHub App install status is checked. If missing, you'll be prompted into the install flow.

Step 2. Connect an error source

Using Sentry

Red dashboard → Project → Integrations → Sentry → "Connect".
Copy the webhook URL and signing secret into Sentry's Internal Integration.
Configure Sentry alert rules to call the webhook for the issues you care about.

Inbound issues automatically create a bug report and kick off analysis.

Manual / agent intake

// Create and analyze in one shot
await tools.red_bug_report({
  action: "create",
  project_id: "...",
  title: "Login endpoint returns 500 on empty password",
  description: "...",
  severity: "high",
  auto_analyze: true
});

Step 3. First fix plan → PR

// Generate a fix plan from the analyzed bug
const plan = await tools.red_bug_fix_plan({
  action: "generate",
  bug_id: "..."
});

// Submit to Purple Codens to produce a PR
const submission = await tools.red_bug_fix_plan({
  action: "submit_to_purple",
  plan_id: plan.id
});
// → workflow run starts and PR URL comes back

Simple single-file fixes can be PR'd directly via red_fix_proposal. Structural or multi-file fixes do better through the Purple chain.

Operational notes

3-Retry loop: if tests fail, the fix is auto-improved up to 3 times. Stops as soon as tests pass.
Slack notifications: link your org's Slack workspace to get completion / failure pings.
External tasks: red_external_task covers non-bug work such as refactors, feature additions, or doc generation.
Blue → Red chain: failed E2E runs can be promoted to bug reports and pushed through Red's pipeline.

Next steps

Red use case

Bug → fix PR flow

Purple chain

The workflow target for submissions

Red tools (4)

Full action list