Shared context for AI agents
Shared context is one place where your AI agents and your teammates keep the same memory, documents, tasks and skills, and search across all of it.
Jacob Cansler · Maker of Gryz
Updated
Short answer: Connect Claude, ChatGPT, Cursor, Codex and any MCP app to one Gryz account. They share the same memory, documents, tasks, skills, notes and search, so what one agent learns, the next one can use. You keep control. You can see what was saved and decide who can reach it.
Start here
Get your agent ready for Gryz
Run the Gryz agent onboarding router after connecting an MCP client, with safe local-write consent and a portable manual fallback.
Docs
MCP setup (Claude, ChatGPT, Cursor, Windsurf, Codex)
Step-by-step MCP connection for Claude.ai, ChatGPT, Cursor, Windsurf, and Codex with OAuth or API key authentication.
Docs
Team and Enterprise
How a company owner decides which AI apps reach company data in Gryz, with the simple Team policy or the stricter Enterprise policy.
Docs
Connect Gryz MCP in Cursor
Complete written walkthrough for adding the Gryz MCP server to Cursor with OAuth, copyable config, troubleshooting, and an optional video demo.
Academy
Connect Gryz MCP in Codex
Complete written walkthrough for adding the Gryz MCP server to OpenAI Codex with OAuth, copyable CLI and TOML, troubleshooting, and an optional video demo.
Academy
Read more
How do I share context between Claude Code and Cursor?
Connect Claude Code and Cursor to Gryz and they share one context for your repo: decisions, docs, tasks and skills. Here's the prompt to paste.
Developers5 min
Context compounds: an AI context layer for teams
Every AI tool your team uses starts from zero. A shared context layer gives people and agents one place to work from, governed by your company.
Company6 min
An AI knowledge base your marketing team owns
Stop pasting the brand guide into every chat. Give ChatGPT and Claude one shared place to read your voice, positioning and past work, under your control.
Company5 min
Shared context for AI coding agents, over MCP
Claude Code in the morning, Cursor after lunch, Codex at night. One MCP connection gives them all the same memory, docs, tasks, skills and search.
Developers6 min
Give every agent a profile: named team members that share your context
Three tools, one shared brain, and no idea which tool saved what. Agent profiles give each one a name, its own key, its own access, and a private memory.
Agent team4 min
Dots vs Grok Bot vs Muse, and what teams of bots still don't share
Three big launches, one missing layer: a shared brain and tool belt you own that every bot can use.
Multi-agent7 min
FAQ
What does shared context include? Memory (the decisions and facts agents save), documents, tasks, skills and private notes, with one search across all of them. The MCP tools reference lists what an agent can do with each.
How is it different from the memory inside one assistant? Memory inside one product stays with that product. Shared context sits outside any one model or chat app, so Claude, ChatGPT, Cursor and Codex all read and write the same place, and it stays with you when you switch.
Which AI tools can use it? Claude, Claude Code, ChatGPT, Cursor, Codex and any app that speaks MCP. Each one connects to the same Gryz server. MCP setup has the steps for each client.
How do I share context between Claude Code and Cursor? Connect both to Gryz, then run Gryz setup in your repo from each one. Gryz keys project memory to your git remote, so both tools see the same facts about the same repo. This post has the exact prompt to paste.
Can a whole team share context? Yes. Company workspaces give people and their agents shared memory, projects, documents, tasks and skills, inside the company's own permissions. They are rolling out to companies now. Team and Enterprise explains how a company decides what each app can reach.
Does it cost anything? MCP access is free with any Gryz account. Plans differ in their limits, such as how much memory and how many private documents you can keep. See pricing.