# Set up self-driving - Docs

**Open beta**

Self-driving is currently in open beta.

Turning on self-driving means connecting the data sources, repositories, and agents that let PostHog ship work for you. It builds on a PostHog project that's already capturing events, so we start there. Most teams are set up in a few minutes.

**Before you start**

You'll need PostHog installed and capturing events and a GitHub repository you want agents to work in.

1.  1

    ## Install PostHog

    Required

    To set up self-driving, you first need to install PostHog and have it capturing events. The fastest way is to use our setup wizard which does the work for you:

    `npx @posthog/wizard@latest`

    [Learn more](/wizard.md)

    If you already have PostHog installed and capturing events, skip ahead. Prefer to set up manually? Follow the [install guide](/docs/getting-started/install.md).

    **AI data processing required**

    Self-driving relies on AI, so your organization needs [AI data processing turned on](/docs/posthog-ai/allow-access.md). The wizard checks this and tells you how to enable it if it's off.

2.  2

    ## Run the self-driving setup

    Required

    On your onboarded project, the self-driving setup enables your signal sources, sets up your scouts, and hands you a link to your inbox.

    `npx @posthog/wizard@latest self-driving`

    [Learn more](/wizard.md)

    The signal sources it can turn on include [error tracking](/docs/error-tracking.md), [session replay](/docs/session-replay.md), and external sources like Zendesk, GitHub Issues, and Linear. The more you enable, the more PostHog can watch to make your product self-driving.

3.  3

    ## Connect Slack

    Recommended

    Add the [PostHog Slack app](/docs/slack.md) so you can summon agents and review their work from your team's channels. You connect your Slack workspace once, and each teammate who wants to ship a pull request connects their own GitHub. PostHog also posts a notification to the **#posthog-inbox** channel whenever a new report lands, so your team sees work as it comes in.

4.  ## Watch your first scout run

    Required

    The wizard hands you a link to your [inbox](/docs/self-driving/inbox.md). From there, scouts run on a schedule and emit [signals](/docs/self-driving/signals.md), related signals group into [reports](/docs/self-driving/reports.md), and those reports land in your inbox ranked by priority and ready to act on.

5.  4

    ## Next step

    You've got a working self-driving setup: scouts watching your data, reports landing in your inbox, and an agent ready to open a pull request for every actionable report. Now head to your inbox to review and merge what lands.

    [Your inbox](/docs/self-driving/inbox.md)

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better