Local transcript authority, explicit team rollups.
Fleetlens is designed so the local machine remains the authority for raw agent history. Team Edition is an optional destination for derived data that the member has chosen to share.
Two operating modes
Private by default
The CLI reads provider-local session files and stores its own usage, entries, digests, and logs under ~/.cclens. No Fleetlens account or database is required.
Shared by explicit pairing
A paired daemon sends selected rollups to a server. The member chooses the project scope during onboarding and can change it or leave the team later.
What can leave the machine?
| Data | Local behavior | Team behavior |
|---|---|---|
| Raw transcripts | Read locally by adapters and local dashboard views. | Not uploaded to Team Edition. |
| Prompts and assistant responses | Remain in provider-local history. | Not uploaded. |
| Absolute paths and file contents | May support local project and code-change signals. | Not uploaded. |
| Daily rollups | Computed locally from session history. | Shared for projects in the member's selected scope. |
| Rich project rollups | Derived from local entries and signals. | Shared as labels and counts, including working shape, skills, subagents, PRs, commits, and pushes. |
| Usage snapshots | Stored in ~/.cclens/usage.jsonl. | Shared for the paired member's plan windows and reset times. |
| AI enrichment | Runs your local claude CLI with your existing Claude Code account when enabled. | Derived outcome/helpfulness fields may be included in selected rollups; raw model conversation is not the sync contract. |
Member controls
- Choose projects during
/team/onboarding. - Review the current selection on the local Team page.
- Change the selection at any time; excluded projects are rebuilt out of future payloads.
- Run
fleetlens team leaveto unpair and stop future team syncing. - Use
fleetlens team logsto see whether a push was accepted, queued, or rejected.
Do not paste device tokens into public issues. Before sharing logs, remove bearer tokens, private project names, absolute paths, and any provider output that your team treats as confidential.
Server responsibilities
Team admins are responsible for the deployment, Postgres backups, encryption key, access control, token revocation, and the team's project-sharing policy. Fleetlens gives the member a selection boundary; it does not decide which repositories your organization considers sensitive.
Follow Sync your first project. The onboarding wizard shows the boundary before the first push begins.