Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cogniscape.app/llms.txt

Use this file to discover all available pages before exploring further.

Cogniscape ingests data from four sources. The CLI captures AI coding activity from Claude Code and Cursor locally; GitHub and Linear webhooks capture code changes and project management activity remotely.

CLI (Claude Code + Cursor)

Sessions, tasks, plans, and token usage — installed per developer machine. Automatically detects and hooks into both Claude Code and Cursor.

GitHub

Pushes, pull requests, and code reviews — one webhook per repository.

Linear

Issues, comments, projects, and cycles — one webhook per workspace.
GitHub and Linear integrations are configured entirely through webhook settings in those platforms. No additional software is needed on your machine — just the webhook URL containing your customer key.

Claude Code vs Cursor: what’s captured

Both AI coding tools feed into the same knowledge graph, but they provide different levels of detail:
CapabilityClaude CodeCursor
Session lifecycle (start/stop)YesYes
Session summary (conversation content)YesYes
Files modified/readYes (from transcript)Not yet (transcript format limitation)
Commands executedYes (from transcript)Not yet
Tool usage countsYes (from transcript)Not yet
Token usage per modelYes (from transcript)Not available (upstream limitation)
Developer identitygit configgit config, falls back to Cursor user email
Repository + branchYesYes
Source discriminationsource="agent"source="cursor"
Events from both tools are distinguishable in the knowledge graph and can be filtered independently in MCP queries.

Where to find your customer key

Your customer key is available in the Cogniscape Customer Portal under your account settings. It is used to route events to your knowledge graph.

Data privacy

Cogniscape only processes event metadata. We never store source code. GitHub webhook payloads contain commit metadata, PR titles, and review comments — not file contents. Linear payloads contain issue titles, descriptions, and project updates. For more details, see Data Privacy.