Supervisor & Backends

The supervisors coordinate backend process lifecycle, health state, and MCP server runtime.

Agent Supervisor

The AgentSupervisor controls CLI and HTTP backend sessions.

Responsibilities

• Start or attach backend sessions.

• Run health checks and expose backend state.

• Auto-restart crashed backends when policy allows it.

• Emit operational events used by diagnostics and audit flows.

Lifecycle

Session Management

Each launch gets a unique session ID (session-{UUID}) so chat history, diagnostics, and backend state remain correlated.

MCP Supervisor

McpSupervisor manages the MCP server independently from AI backends.

Features

• Health checks with bounded restart attempts.

• Existing-server detection and safe handover on occupied ports.

• SSE and STDIO transport lifecycle.

• Optional TLS with local loopback trust handling.

• Explicit state transitions: Starting -> Running/Failed -> Stopped.

Backend Types

CLI Backends

• Run as subprocesses from configured commands.

• Use stdout/stderr streaming for response and diagnostics.

• Include Gemini CLI, Claude CLI, Codex CLI, OpenCode CLI.

HTTP Backends

• Connect to HTTP APIs of running servers.

• Optionally auto-start local services (provider-dependent).

• Include Ollama, LM Studio, and Generic OpenAI-compatible.

Failure Handling

• Immediate startup exit: marked as crashed; usually indicates config/auth/command errors.

• Runtime crash: restart attempts follow backoff policy.

• Crash suppression: repeated failures disable restart loops.

• Manual control: restart remains available from UI.

Diagnostics

Backend diagnostics include:

• process exit code,

• last stdout/stderr lines,

• launch configuration details.

Use Burp's extension output/errors tabs for investigation.