public active Last verified 2026-04-07

Topolo BugFix

Public overview of BugFix, including AI-assisted bug analysis, fix generation, and Nexus-backed provider usage.

Owners
ai-platform
Source Repos
PlatformApplications/TopoloBugFix, PlatformApplications/TopoloDocs
Systems
Topolo Auth, Topolo BugFix, Topolo Nexus
Tags
bugs, ai, automation, github

What It Is

Topolo BugFix is the bug analysis and fix-automation application in the Topolo portfolio. It accepts bug reports, generates candidate fixes with AI, and can open pull requests for human review.

Architecture

BugFix runs as a worker-backed application with D1 persistence for reports, fixes, validations, and pull-request metadata. AI generation now routes through Nexus rather than calling Anthropic or OpenAI directly from the BugFix worker.

Runtime Surfaces

  • BugFix worker API
  • D1-backed bug, fix, validation, and PR data
  • Nexus gateway for AI provider access
  • GitHub for branch and PR automation

API Surface

Primary route families include:

  • /api/reports
  • /api/fixes
  • /api/admin/queue
  • /webhooks/github
  • /webhooks/validation

API Reference

BugFix currently uses curated route coverage rather than a published OpenAPI surface in PlatformApplications/TopoloDocs.

AI Generation

BugFix uses Nexus for AI-backed fix generation and validation. Product-specific prompt logic, JSON parsing, confidence handling, and GitHub workflows remain local to BugFix, while provider invocation and usage attribution move through Nexus.

Auth and Permissions

Authenticated review and generation paths use user auth. Background or auto-triggered AI flows use trusted service-context calls into Nexus with explicit organization and optional user attribution.

Data Ownership

BugFix owns bug reports, generated fixes, validations, and PR workflow state. Nexus owns provider access and usage attribution.

Deployments

BugFix deploys as a Cloudflare Worker. AI generation depends on Nexus gateway reachability plus a trusted Nexus service token for server-side attribution flows.

Failure Modes

  • report has no organization context for Nexus attribution
  • Nexus service token or gateway configuration is missing
  • provider failure prevents fix generation or validation
  • GitHub PR creation succeeds or fails independently of AI generation

Debugging

  • confirm BugFix can reach Nexus and has a valid service token
  • verify bug reports include org_id for auto-triggered AI generation
  • inspect Nexus usage logs before checking provider dashboards
  • inspect BugFix report and fix statuses if generation fails mid-flow

Change Log / Verification

  • Verified against the current Nexus-backed BugFix generation flow on 2026-03-29