Skip to main content
Cogniscape ingests data from multiple sources. The CLI captures AI coding activity from Claude Code and Cursor locally; GitHub, GitLab, Linear, Jira, and Monday.com 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.

GitLab

Pushes, merge requests, pipelines, and deployments — one webhook per project, or one per group.

Linear

Issues, comments, projects, and cycles — one webhook per workspace.

Jira

Issues, comments, worklogs, sprints, projects, and versions — one webhook per Jira site.

Monday.com

Board items, updates, and column changes — one webhook per board.
GitHub, GitLab, Linear, Jira, and Monday.com 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. Jira also requires a signing secret (Cloud) or the X-Cogniscape-Token header (Data Center / Server).

​
Claude Code vs Cursor: what’s captured

Both AI coding tools feed into the same knowledge graph, but they provide different levels of detail: 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 and GitLab webhook payloads contain commit metadata, PR/MR titles, and review comments — not file contents. Linear, Jira, and Monday.com payloads contain issue/item titles, descriptions, and status updates. For more details, see Data Privacy.