Troubleshooting

Agent Context

If an agent starts a session without project memory, ask it to call the unified bootstrap tool first. This is the canonical path for every MCP client.

{
  "tool": "remb__session_start",
  "arguments": {
    "mode": "lean",
    "project_slug": "your-project-slug"
  }
}

MCP Tools

tools/list returns the core Remb tools by default. If a task needs a narrower or more specialized catalog, request a ranked list and use tool_discover for the rest.

{
  "method": "tools/list",
  "params": {
    "_meta": {
      "tool_budget": 20,
      "context_hint": "debug a failed GitHub-backed scan"
    }
  }
}

Scan Recovery

A scan that stalls or fails is usually caused by GitHub token access, a branch mismatch, worker dispatch failure, or a long-running job that needs to be stopped.

• Open the scan detail page and read the latest error log.
• Confirm the project branch still matches the GitHub default branch or intended branch.
• Reconnect GitHub if repository access or token freshness is in doubt.
• Stop a stuck running scan before starting a fresh one.

Scan-on-Push

Scan-on-push requires a per-project webhook secret. Remb refuses unsigned push deliveries for projects that are missing that secret.

{
  "tool": "remb__scan_on_push",
  "arguments": { "project_slug": "your-project", "enabled": false }
}

{
  "tool": "remb__scan_on_push",
  "arguments": { "project_slug": "your-project", "enabled": true }
}

Support Bundle

When reporting a problem, include the project slug, scan id, last visible scan log, client name, and whether the agent successfully called session start.