Four ingestion points
Cogniscape automatically captures activity from the places where development actually happens:Claude Code
Sessions, plans, tasks, token usage, and session summaries — captured via hooks on the developer’s machine.
Cursor
Sessions and conversation summaries — captured via Cursor hooks, automatically detected during installation.
GitHub
Pushes, pull requests, and code reviews — captured via repository webhooks.
Linear
Issues, comments, projects, and project updates — captured via workspace webhooks.
How it works
Query from any MCP-enabled tool
Once events are in the graph, you retrieve context through the Cogniscape MCP — available in any tool that supports the Model Context Protocol, including Claude Code, Claude Desktop, OpenAI Codex, and others. Ask things like:- “What did the team deliver this week? Summarize completed issues, merged PRs, and any blockers.”
- “What is our average cycle time from opening an issue to merging the PR? Which items are taking the longest, and why?”
- “Is the team on track to finish the current sprint? Which issues haven’t had any activity in the last 3 days?”
- “How much of our engineering effort is going to new features versus bug fixes versus infrastructure? Has that changed compared to last month?”
- “How much of our codebase is being built with AI assistance? What is the concrete return on that investment?”
- “How efficient is our code review process? How many PRs required rework, and what are the most common reasons?”
Get started
Quick Setup
Install the CLI and start capturing Claude Code and Cursor activity automatically.
CLI Reference
Full reference for all cogniscape commands and flags.
GitHub Integration
Set up a webhook to capture pushes, PRs, and code reviews.
Linear Integration
Set up a webhook to capture issues, comments, and project updates.
Cogniscape MCP
Query the knowledge graph from Claude Code, Claude Desktop, or any MCP client.