Autonomous multi-agent software debugging platform for real-world engineering issues.
Code Debugger AI is a full-stack autonomous multi-agent software engineering assistant built to analyze, diagnose, and propose fixes for real-world development problems.
Instead of focusing only on simple code bugs, this platform is designed for broader software engineering scenarios such as:
- code bugs
- code review issues
- test failures
- API errors
- CI/CD failures
- performance issues
- deployment incidents
The system combines:
- a dark, product-style frontend built with Next.js
- a FastAPI backend for orchestration
- Gemini-powered reasoning agents
- SQLite for internal issue history
- Pinecone for semantic memory retrieval
The result is a project that demonstrates full-stack development, multi-agent system design, retrieval-augmented workflows, AI-assisted debugging, and modern software architecture.
A developer submits an engineering issue through the UI, including:
- issue type
- project name
- error summary
- detailed problem description
- code snippet, logs, config, command, or workflow YAML
The platform then runs a multi-agent workflow:
-
Planner Agent Creates a structured investigation plan based on issue type.
-
Retrieval Agent Pulls relevant context from:
- internal SQLite issue history
- Pinecone semantic memory
- issue-type-specific debugging heuristics
-
Analysis Agent Uses Gemini to identify the most likely root cause, affected system area, and next debugging checks.
-
Patch Agent Uses Gemini to propose a practical repair, config change, workflow fix, or patch preview.
-
Review Agent Uses Gemini to critique the proposed solution, estimate confidence, classify risk, and recommend validation steps.
The frontend then displays:
- workflow results
- memory hits
- semantic matches
- patch suggestions
- review confidence
- risk level
- autonomy signals
- Planner Agent
- Retrieval Agent
- Analysis Agent
- Patch Agent
- Review Agent
bugcode_reviewtest_failureapi_errorci_cd_issueperformance_issuedeployment_issue
- Gemini-powered root cause analysis
- Gemini-powered patch suggestions
- Gemini-powered dynamic review and validation guidance
- SQLite memory for past issue history
- Pinecone semantic similarity search
- retrieval-aware debugging context
- dark blue developer-focused interface
- dedicated pages for:
- Dashboard
- New Issue
- Agent Workflow
- Patch Review
- Knowledge Memory
- workflow branching by issue type
- retry/fallback logic
- memory-aware retrieval
- handoff visibility across agents
Current MVP input supports:
- text issue descriptions
- logs
- stack traces
- code snippets
- config files
- commands
- workflow YAML
Planned multimodal expansion:
- screenshots of errors
- architecture diagrams
- terminal screenshots
- deployment dashboard images
- API screenshots
- uploaded files and visual debugging context
This means the architecture is already positioned to grow into a multimodal developer support system, not just a text-only bug analyzer.
sequenceDiagram
participant User
participant Frontend
participant Backend
participant Planner
participant Retrieval
participant Analysis
participant Patch
participant Review
participant Gemini
participant SQLite
participant Pinecone
User->>Frontend: Submit issue
Frontend->>Backend: POST /agent-workflow
Backend->>Backend: Save issue
Backend->>Planner: Build plan
Backend->>Retrieval: Gather context
Retrieval->>SQLite: Query similar issues
Retrieval->>Pinecone: Query semantic matches
Backend->>Analysis: Analyze issue
Analysis->>Gemini: Root cause reasoning
Backend->>Patch: Generate fix
Patch->>Gemini: Patch suggestion
Backend->>Review: Review solution
Review->>Gemini: Confidence + risk + validation
Backend->>Frontend: Return workflow result
Frontend->>User: Show output cards
flowchart TD
U["User / Developer"]:::user --> UI["Dark UI Dashboard<br/>Next.js Frontend"]:::frontend
UI --> API["FastAPI Backend + Proxy Route"]:::backend
API --> P["Planner Agent"]:::agent
API --> R["Retrieval Agent"]:::agent
API --> A["Analysis Agent"]:::agent
API --> PA["Patch Agent"]:::agent
API --> RV["Review Agent"]:::agent
R --> SQL["SQLite Internal Memory"]:::memory
R --> PC["Pinecone Semantic Memory"]:::memory
A --> G["Gemini API"]:::llm
PA --> G
RV --> G
API --> OUT["Workflow Output<br/>Confidence • Risk • Patch • Memory Hits"]:::output
OUT --> UI
classDef user fill:#0f172a,color:#ffffff,stroke:#93c5fd,stroke-width:2px;
classDef frontend fill:#1d4ed8,color:#ffffff,stroke:#bfdbfe,stroke-width:2px;
classDef backend fill:#0f766e,color:#ffffff,stroke:#99f6e4,stroke-width:2px;
classDef agent fill:#7c3aed,color:#ffffff,stroke:#ddd6fe,stroke-width:2px;
classDef memory fill:#15803d,color:#ffffff,stroke:#bbf7d0,stroke-width:2px;
classDef llm fill:#b45309,color:#ffffff,stroke:#fde68a,stroke-width:2px;
classDef output fill:#be123c,color:#ffffff,stroke:#fecdd3,stroke-width:2px;
- Next.js
- React
- TypeScript
- Custom CSS
- Local workflow history in browser storage
- Python
- FastAPI
- Pydantic
- Uvicorn
- Gemini API
- Pinecone
- SQLite
- multi-agent orchestration
- retrieval-augmented reasoning
- semantic memory
- branching workflows
- fallback logic
- progressive autonomy
code-debugger/
frontend/
app/
api/
dashboard/
new-issue/
agent-workflow/
patch-review/
knowledge-memory/
globals.css
layout.tsx
page.tsx
components/
Sidebar.tsx
Topbar.tsx
lib/
workflow-store.ts
backend/
app/
agents/
planner_agent.py
retrieval_agent.py
analysis_agent.py
patch_agent.py
review_agent.py
api/
routes.py
core/
config.py
db/
database.py
models/
issue.py
services/
agent_workflow.py
issue_service.py
llm_service.py
pinecone_service.py
main.py
requirements.txt
.env
docs/
Shows:
- recent workflow runs
- average confidence
- memory hit counts
- latest run overview
Allows users to submit:
- issue type
- project name
- summary
- details
- code / config / commands
Displays:
- planner output
- retrieval reasoning
- analysis response
- patch generation
- review output
Shows:
- patch preview
- confidence
- risk
- validation steps
Shows:
- SQLite memory hits
- Pinecone semantic matches
- recent stored runs
Example:
- incorrect arithmetic logic
- broken conditions
- edge-case failure
Example:
- maintainability concerns
- duplication
- unclear structure
- weak naming
Example:
- failing unit test
- assertion mismatch
- flaky test setup
Example:
- 422 validation failures
- schema mismatch
- request parsing errors
- alias/field issues
Example:
- GitHub Actions failures
- dependency install issues
- environment variable problems
- pipeline misconfiguration
Example:
- repeated work
- inefficient loops
- slow queries
- missing caching
Example:
- broken health checks
- wrong port binding
- startup crashes
- container misconfiguration
The platform uses two memory layers:
Used for:
- internal issue history
- recent stored runs
- structured lookup by issue type or project
Used for:
- semantic retrieval of similar incidents
- context-aware debugging
- matching related engineering problems across past runs
This separation allows the system to combine:
- exact structured memory
- semantic engineering memory
This project uses semi-autonomous specialized agents.
Current autonomy features:
- issue-type-aware branching
- structured handoffs between agents
- LLM-backed reasoning
- retry/fallback behavior
- memory-aware retrieval
Current limitations:
- agents do not yet dynamically choose external tools
- agents do not inspect entire repos automatically
- no autonomous shell or browser tool use yet
- no long-running self-correction loops yet
This is intentional for the MVP: the system is complex enough to be meaningful, but still understandable and demoable.
The project currently supports:
- full-stack workflow from UI to backend
- real backend issue submission
- structured issue storage
- real multi-agent orchestration
- Gemini-powered reasoning in multiple agents
- dynamic review confidence/risk
- SQLite memory storage
- Pinecone semantic retrieval
- dark UI for developer workflows
- visible autonomy and memory signals
Create a .env file inside backend/:
GEMINI_API_KEY=your_gemini_api_key
PINECONE_API_KEY=your_pinecone_api_key
PINECONE_INDEX_NAME=code-debugger-memorycd backend
py -m uvicorn app.main:app --reloadcd frontend
npm run dev- Frontend:
http://localhost:3000 - Backend:
http://127.0.0.1:8000
- service fails readiness checks
- wrong container port
- localhost binding issue
- DB unavailable during startup
- GitHub Actions dependency issues
- private package auth issues
- missing CI environment variables
- 422 response after schema evolution
- alias mismatch
- missing nested fields
This project is not just a chatbot UI.
It demonstrates:
- agent architecture design
- full-stack engineering
- LLM orchestration
- semantic retrieval
- memory-aware debugging
- developer tooling UX
- structured issue analysis for real engineering workflows
It is meant to show how AI systems can support software engineers with:
- diagnostics
- patch generation
- review
- context retrieval
- engineering decision support
Although the current implementation is mostly text-driven, the product is designed to evolve toward multimodal software debugging.
- issue descriptions
- code snippets
- logs
- stack traces
- YAML configs
- deployment configs
- commands
- screenshots of runtime errors
- CI/CD dashboard screenshots
- browser console screenshots
- architecture diagrams
- terminal screenshots
- uploaded files
- API screenshots
- observability chart snapshots
Many real-world software issues are easier to diagnose with visual context:
- cloud dashboards
- deployment status screenshots
- browser errors
- tracing screenshots
- monitoring graphs
Adding multimodal retrieval and analysis would make the system much closer to a true AI software engineering copilot.
- tool-using agents
- dynamic workflow branching by confidence score
- confidence-based retries
- adaptive skipping of irrelevant agents
- agent debate / consensus mode
- real repo ingestion
- file-level code search
- AST-aware analysis
- automatic diff generation from repo context
- stronger Pinecone indexing strategy
- metadata filtering
- better similarity tuning
- project-specific memory namespaces
- image upload support
- screenshot analysis
- file upload support
- diagram-aware reasoning
- PostgreSQL for persistent production storage
- auth / user accounts
- organizations / workspaces
- run history API
- background task queue
- markdown rendering for agent outputs
- collapsible workflow trace panels
- better code diff viewer
- saved issue history page
- one-click demo examples
- cloud deployment
- shareable public demo
- observability dashboards
- audit logs
- agent performance analytics
This project demonstrates:
- full-stack development with Next.js and FastAPI
- multi-agent system architecture
- real LLM integration with Gemini
- semantic retrieval with Pinecone
- memory-aware debugging workflows
- dynamic review and patch pipelines
- product-oriented UI/UX for developer tooling