Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.charlielabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

Use this page for fast triage when Charlie is not responding or output doesn’t match expectations.

​
Fast triage checklist

  1. Confirm the repo is in scope for your GitHub App installation.
  2. Confirm the triggering user has the required permissions on that surface.
  3. Confirm Charlie was explicitly invoked (mention/review request/assignment) when needed.
  4. Confirm required integrations are connected for the workflow you expect.
  5. Re-run the request with a concrete, scoped instruction.
For daemon-specific rollout/debugging, use Testing and iterating on daemons.

​
Common issues → next action

​
Run failed mid-task

  • Read the failure message in the thread.
  • Re-trigger with explicit continuation context (what failed + what to try next).
  • If failures repeat, include exact command output in your follow-up.

​
Charlie not visible in Linear assignee/search

  • Invite Charlie to the Linear workspace and the specific team.
  • Recheck workspace/team linkage in your integration settings.

​
No response on GitHub

  • Verify CharlieCreates is installed on that repo.
  • Confirm the event is one Charlie responds to (mention, review request, assignment, eligible PR event).
  • Confirm the sender has sufficient permissions for that repo context.

​
Mention doesn’t trigger

  • Use @CharlieHelps exactly in a supported comment/review context.
  • If using review comments, ensure it’s in a submitted review context when required.

​
Charlie says it committed, but no commit appears

  • Check branch protection and required status rules.
  • Check whether local commit hooks or verification steps failed before push.
  • Ask Charlie to report branch name + exact failed command output.

​
CI mismatch (Charlie passed locally, CI failed)

  • Compare environment variables and runtime versions between devbox and CI.
  • Ask Charlie to reproduce using the same script target CI runs.

​
External CI logs (non-GitHub Actions)

  • Paste failing log excerpts or attach machine-readable test artifacts in-thread.
  • Ask Charlie to diagnose from that output and propose/apply a fix.

​
Escalation checklist

If you contact support, include:
  • Where it was triggered (GitHub/Linear/Slack + link)
  • The failing message or error text
  • What you already tried (steps + outcomes)
Send details to support@charlielabs.ai.