Skip to main content
Below are solutions to the most frequent hurdles teams run into when getting Charlie up and running. If your question isn’t answered here, reach out on our shared Slack channel or email support@charlielabs.ai.
When Charlie fails, he will tell you what to do next. Usually, he asks you to reply by mentioning him and saying please continue.If Charlie fails multiple times and your account is properly set up, please contact support.
Charlie must be invited to your Linear workspace and team before he can comment or be assigned issues.Fix
  1. In Linear, go to Settings → Teams → (choose your team) → Members.
  2. Click Invite member → search for Charlie (charlie@charlielabs.ai).
  3. Give him the Contributor role (minimum).
  4. Re-run the action; Charlie should now show up in assignee menus.
  • Make sure CharlieHelps has been invited to the repo (or is a member of the organization).
    • “Read” permissions are all the helper account needs.
    • If the invite hasn’t been accepted in 15 minutes, reach out to support. This is typically caused by organizations having strict secrurity policies around invites.
Charlie reports “Committed changes to branch xyz” in the PR timeline, yet no new commits show up on GitHub. The most common culprit is a local pre-commit hook that fails after the commit is created.
  • a script relying on Bash-specific features while being invoked with plain sh, or
  • a Windows-style line ending in the shebang line (e.g. #!/bin/sh saved with CRLF).
When the hook exits non-zero Git aborts the commit, so nothing is pushed.Fix
  • Ensure every script is POSIX compliant.
  • Ask Charlie to scan the repository for non-POSIX compliant scripts or script templates and open a PR to update them to POSIX compliance.
There is no stop button (yet)—once a Charlie run starts it will keep running until it either completes or errors out.

​
If you need to get back to a clean slate

  • Wait until Charlie finishes.
  • Then reset, revert, or manually edit the commits he pushed.
  • Ask Charlie—leave a comment on the pull request requesting that he reset, revert, or edit the commits for you.

​
Alternative workaround

  • Create a new branch from the current HEAD and continue your work there while Charlie completes its run on the original branch.

​
Heads-up on force pushes

Charlie pushes with git push --force-with-lease. If you manually force-push over his work before the run ends, Charlie’s next push will overwrite your changes.
⌘I