> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Set up Agent Insights
> Connect coding-agent activity, map members, preview a sync, and verify Agent Insights with a small pilot.
Start with a few volunteers and one project. Confirm what will be collected, verify the first sync, and fix attribution before expanding access.
## 1. Choose a collection path
| Path | Best for |
| ---------------------------- | ----------------------------------------------------------- |
| **Entelligence CLI** | Supported session data stored on developer machines |
| **Provider connection** | Organization-level analytics available from the coding tool |
| **OpenTelemetry** | Centralized Claude Code or compatible agent traces |
| **Observability connection** | Agent traces already collected in a supported platform |
Available sources depend on your workspace and coding agents.
## 2. Install and authenticate
```bash theme={null}
curl -fsSL https://app.entelligence.ai/install.sh | sh
entelligence auth login
entelligence auth status
```
## 3. Index and analyze local sessions
```bash theme={null}
entelligence insights setup
entelligence insights index --source local
entelligence insights analyze
```
## 4. Preview before syncing
```bash theme={null}
entelligence insights sync --dry-run
```
Check the proposed records, time window, identity, and fields. When the preview looks right:
```bash theme={null}
entelligence insights sync
entelligence insights schedule --at 09:00
```
The local CLI path syncs computed insight fields rather than raw prompts, responses, or tool input/output. Confirm the current field list for your workspace before a broad rollout.
## 5. Map members
Open **Settings → Team**, select the relevant coding-agent tab, and map each provider identity to the correct Entelligence member. Refresh mappings when members or provider identities change.
## 6. Verify the first sync
Confirm that:
* Expected repositories and projects appear.
* Unattributed activity is understood or corrected.
* Tokens, sessions, and spend look plausible.
* Member tools and last activity match the pilot.
* Project targets and mappings use the intended source.
Confirm the selected date range and timezone before interpreting when activity happened.
## Next step
Read [metrics and data](/agent-insights/metrics), then establish [privacy and governance](/agent-insights/privacy).