Overview
What Jackdaw is, how it maintains the current state, and where to start.
Jackdaw is the shared operating context for teams and their agents. It brings together decisions, plans, people, evidence, and changes from the places work already happens; helps the right people establish what is current; and gives every connected person and agent the same source-backed state.
Jackdaw is in closed beta. Everything here is available to beta users today unless a piece is marked otherwise — nothing is generally available yet.
The problem it solves
Teams rarely lack information. They lack a reliable way to maintain what the information now means.
Work is scattered across meetings, messages, documents, projects, and people’s heads. Decisions get revised, conditions change, and old versions remain visible. People compensate with status meetings and repeated briefings. AI can retrieve every fragment without knowing which one won, who had authority to settle it, or whether uncertainty should stop the work.
Jackdaw turns that fragmented history into a current operating picture that people can inspect and agents can safely use.
How the pieces fit together
| Piece | What it does | Status |
|---|---|---|
| Wiki | Keeps the work, decisions, owners, evidence, and history on connected pages people and agents can use together | In beta |
| Connections | Bring in relevant information from email, calendar, documents, code, chat, and other tools | In beta |
| Memory Engine | Connects related evidence, tracks what replaced what, and brings conflicts to the right people to resolve | In beta |
| Agents | Own ongoing missions and duties from the team’s current state, within explicit boundaries | In beta |
| MCP server | Lets compatible AI tools read context, save facts you state, suggest properties, and edit existing document pages with citations | In beta |
| Coding-tool plugin | Adds relevant context and session capture to Claude Code, Codex, and Cursor | In beta |
| Browser extension | Brings relevant Jackdaw context into Claude.ai and ChatGPT as you work | Closed beta |
The operating loop
Jackdaw supports one continuous cycle:
- Bring the work in. Connect the systems where decisions, evidence, and changes already live.
- Find what diverged. Jackdaw connects related information and surfaces competing versions or missing context.
- Settle it with authority. The appropriate person confirms what is current and what remains unresolved.
- Put the result to work. People and agents use the same decision, evidence, conditions, and boundaries.
- Bring learning back. Facts you state can save directly; inferred claims and conflicts come back for review.
Where to start
- Connect your sources — start with two or three places where real decisions and changes appear.
- Browse your wiki — choose one active project and inspect its decisions, owners, evidence, and open questions.
- Review what Jackdaw found — resolve one useful change or conflict so the current state is explicit.
- Put that context to work — build an agent in Jackdaw or connect an AI over MCP.
New here? Getting Started walks through the loop end to end.
Learn by doing
- Build a project page your team can use — establish a goal, decision, blocker, and source in one place.
- Trace a decision to its source — compare a preserved document with Jackdaw's extracted claim and review it.
- Share one useful fact with your team — decide whether a scoped fact belongs with everyone in a shared workspace.
- Connect Claude.ai — let an external AI retrieve your current context over MCP.
- Claude memory is full? — move the durable facts you still need into Jackdaw and let Claude retrieve them.
- Use one memory across Claude, Codex, and Cursor — connect three coding tools to the same current project context.
- Keep a decision after your AI forgets the chat — preserve the choice, reason, and source for a new coding session.
- Fix a one-time comment saved as a permanent memory — remove an overbroad Claude Code memory and keep only durable context.
For feature details, see Page types, Source documents and evidence, Workspace sharing suggestions, and the Wiki guide.
Workspaces
A workspace is the boundary around a group of people, their connected sources, and the context they are allowed to share. Use separate workspaces for personal, family, and team contexts. Nothing crosses those boundaries unless you deliberately put it there. See Workspaces & teams for details.
The browser extension is not open yet. If you are a beta user and want early access when it lands, reach out.