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

# Installation

> Set up Charlie with GitHub, then connect optional integrations.

Charlie has two offerings:

* **Agents** for on-demand work (mentions, assignments, review requests)
* **Daemons** for scheduled or watch-based automation

To run Charlie, complete the required setup below: sign in, connect GitHub OAuth, and install/scope the `CharlieCreates` GitHub App on the repos Charlie should access.

## Required setup

<Steps>
  <Step title="Sign in to the dashboard">
    Go to <a href="https://dashboard.charlielabs.ai">dashboard.charlielabs.ai</a> and create your account.

    Use a valid team email so Charlie can map the right org/workspace access.
  </Step>

  <Step title="Connect GitHub OAuth">
    During onboarding, authorize GitHub OAuth for the account you'll use to install and manage Charlie.

    This lets Charlie verify your access and keep repo-level permissions aligned with GitHub.
  </Step>

  <Step title="Install the GitHub App on the repos you want Charlie to access">
    Install <a href="https://github.com/apps/charliecreates">CharlieCreates</a> and scope access to the exact repositories where Charlie should run.

    You can start narrow and add more repositories later.
  </Step>
</Steps>

## Recommended GitHub user setup

Inviting <a href="https://github.com/CharlieHelps">CharlieHelps</a> is optional, but recommended when you want teammates to mention Charlie, request Charlie’s review, assign work to Charlie in GitHub, or see Charlie in GitHub autocomplete.

`CharlieCreates` remains the required GitHub App that grants repo-scoped access and powers most GitHub actions. `CharlieHelps` is the GitHub user that makes GitHub’s people-oriented UI work. Repo-scoped app actions and app-backed or scheduled daemon workflows are not blocked on the user invite. Many teams invite both; see <a href="/integrations/github-identities">GitHub App and user</a> for the comparison.

<Note>
  Using Charlie on public/open-source repositories? Review <a href="/open-source">Open Source</a> first, then follow your org’s security policy for GitHub App scope and token handling.
</Note>

## Optional but recommended integrations

You can use Charlie with GitHub only, but most teams also connect:

* [Linear](/integrations/linear)
* [Slack](/integrations/slack)
* [Sentry](/integrations/sentry)
* [Vercel](/integrations/vercel)

See the [Integrations](/integrations) hub for setup paths.

If you want Linear events to wake daemon `watch` conditions, connect Linear and map the relevant Linear team(s) to the repo where the daemon lives. For Slack event wakes, connect Slack and map the Slack workspace to that repo. GitHub-only setup supports GitHub-routed events and scheduled daemon wakes, but not Linear or Slack event wakes.

## Daemons setup

If you want scheduled or watch-driven automation, continue to [Daemons](/daemons).