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. For Linear workflows, confirm the issue’s Linear team is mapped to the intended repo. For Slack workflows, confirm the Slack workspace is mapped to the intended repo.
  6. 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 any Linear teams where you expect him to appear.
  • Recheck the relevant Linear team mapping 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.

​
No response on Linear

  • Confirm the Linear integration is connected.
  • Confirm the issue’s Linear team is mapped to the intended repo.
  • For a direct request, use @Charlie in a supported issue comment, or assign the issue to Charlie when assignment is the intended action.
  • For a daemon wake, confirm the new issue or issue comment matches the daemon watch; issue comments do not need to mention Charlie.
  • Confirm the sender can access both the Linear issue and the mapped repo context.

​
No response on Slack

  • Confirm the Slack integration is connected.
  • Confirm the Slack workspace is mapped to the intended repo.
  • Confirm Charlie can access the channel, thread, or DM where the request was made.
  • Use @Charlie for direct asks in Slack. For daemon watches on broader channel messages, make sure daemon watch wording or body policy narrows the wake to intentional channels.

​
Daemon didn’t wake from a Linear or Slack event

  • Confirm the daemon file is merged on the repo default branch and has been ingested by Charlie.
  • For Linear, confirm the integration is connected and the issue’s Linear team maps to the intended repo. For Slack, confirm the integration is connected and the Slack workspace mapping points to the intended repo.
  • Confirm the event is supported context: Linear issue creation, issue comments on mapped issues, including comments that do not mention Charlie, issue mentions, and issues assigned to Charlie; or Slack mentions/thread replies, channel messages, and DMs.
  • Confirm the triggering user and Charlie have permission to read the source issue, channel, thread, or DM.
  • Make the watch entry concrete and provider-visible, such as “A Linear issue is created” or “A Linear issue comment is added on an issue.”

​
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.