> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enfors.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Connect Claude Code and Claude Desktop to Enfors and see decisions flow in.

Enfors captures **Claude Code and Claude Desktop** with a lightweight local **watcher** that
reads their session transcripts — no proxy, no certificate to trust. (Agent SDKs like the
OpenAI SDK integrate separately, by calling the Enfors gateway directly.)

<Info>
  **Prerequisites** — macOS or Windows, with Python 3 (the installer installs it
  automatically if it's missing — via [Homebrew](https://brew.sh) on macOS, via winget on
  Windows), and an Enfors workspace (sign in with SSO).
</Info>

## 1. Run the installer

<Tabs>
  <Tab title="macOS">
    ```bash theme={null}
    curl -fsSL https://get.enfors.ai/install.sh | zsh
    ```
  </Tab>

  <Tab title="Windows (PowerShell)">
    ```powershell theme={null}
    irm https://get.enfors.ai/install.ps1 | iex
    ```
  </Tab>
</Tabs>

The installer is idempotent, and detects and supersedes any earlier proxy-based install.

<Steps>
  <Step title="Install Python 3">
    Detected, or installed automatically if missing. The watcher is a single file with no
    third-party dependencies.
  </Step>

  <Step title="Install the watcher">
    `~/.enfors/hooks/enfors_watcher.py` is installed and registered to run at login — a
    LaunchAgent (`ai.enfors.watcher`) on macOS, a Scheduled Task (`EnforsWatcher`) on
    Windows — so it captures Claude Code + Claude Desktop by reading their transcripts.
  </Step>

  <Step title="Sign in with SSO">
    A browser opens the Cognito PKCE flow (callback on `localhost:8765`). Tokens are cached
    to `~/.enfors/hooks/tokens.json` and refreshed automatically.
  </Step>

  <Step title="Add the Enfors MCP">
    The installer registers the Enfors MCP server in Claude Code and Claude Desktop, so you
    can query Enfors from inside your tools.
  </Step>
</Steps>

<Frame caption="Installer flow — SSO sign-in">
  <img src="https://mintcdn.com/enfors/Klv0sMKyL34AsmTT/images/installer-sso.svg?fit=max&auto=format&n=Klv0sMKyL34AsmTT&q=85&s=ffe3dfcacfb3fa155ea733141f7476ba" alt="Enfors installer SSO step" width="1200" height="750" data-path="images/installer-sso.svg" />
</Frame>

## 2. Use your tools normally

Work in Claude Code or Claude Desktop as usual. When a turn completes, the watcher reads it
from the local session transcript and uploads it to `data.enfors.ai`, where Enfors
reconstructs it into a **decision**.

Nothing changes in your workflow, and your tools never wait on Enfors.

## 3. See your workforce in Enfors

Open the app and watch the **live workspace view**: agents active, work run today, current
spend, and a breakdown of outcomes.

<CardGroup cols={2}>
  <Card title="Leader lens" icon="chart-line" href="/using/leader-lens">
    Live status, Pulse reports, and ask-in-plain-English queries.
  </Card>

  <Card title="Builder lens" icon="magnifying-glass" href="/using/builder-lens">
    Drill into a session's decisions, logic trace, and evidence.
  </Card>
</CardGroup>

## Manage the watcher

The installer adds an `enfors` command-line tool — identical on macOS and Windows:

```bash theme={null}
enfors login     # sign in with SSO (opens browser; caches token)
enfors check     # is the watcher running?
enfors start     # start it (and re-enable it at login)
enfors stop      # stop it (and disable it at login, until you start it again)
enfors logs      # tail ~/.enfors/hooks/watcher.log
```

See [Managing credentials](/admin/credentials) for the full CLI reference, and
[Uninstall](/admin/uninstall) to remove the watcher.

## Next steps

<CardGroup cols={2}>
  <Card title="How Enfors works" icon="sitemap" href="/getting-started/how-enfors-works">
    Understand the pipeline behind the gateway and the watcher.
  </Card>

  <Card title="Connect your tools" icon="plug" href="/integrations/clients">
    Per-client setup for Claude Code and Claude Desktop.
  </Card>
</CardGroup>