Skip to main content
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

Available sources depend on your workspace and coding agents.

​
2. Install and authenticate

​
3. Index and analyze local sessions

​
4. Preview before syncing

Check the proposed records, time window, identity, and fields. When the preview looks right:
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

Repository and project spend attributed after an Agent Insights 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, then establish privacy and governance.