Skip to main content
If you build alone with a handful of coding agents, each one starts every session knowing nothing. One agent learns that a webhook handler must stay idempotent, and the next agent, in another tool, breaks it the following day. This recipe connects all of your agents to one Graphify workspace, so they read the same code graph and the same notes about your code.
Works with: Graphify (hosted), with any mix of Claude Code, Codex, Cursor, VS Code and cloud coding agents.

​
The short version

Connect each agent to https://api.graphify.com/mcp, then paste this into any of them: Every agent should report the same workspace and repositories.

​
The scenario

A solo founder runs one product across three repositories: a web app, an API and a mobile app. Claude Code does most feature work, Codex handles background tasks, and Cursor is open for quick edits. Each agent has its own memory file, and none of them agree. The founder wants one place that every agent reads before it changes code.

​
What you’ll build

  • Every agent connected to the same Graphify workspace through the hosted MCP server.
  • One shared instruction block, committed to each repository, that every agent reads.
  • A habit of recording decisions once, in Graphify memory, so the next agent finds them.

​
Before you start

  • Your repositories indexed in one Graphify workspace.
  • The agents you use. Setup for each client is in Hosted MCP.

​
Setup

1

Connect every agent to the same endpoint

Add https://api.graphify.com/mcp to each agent and sign in with the same Graphify account. For cloud agents, follow Connect cloud coding agents to hosted MCP.
2

Pin the workspace

If you belong to more than one Graphify workspace, ask each agent to call list_workspaces. If the wrong one is active, set_workspace switches it for the session, and make_default makes it stick across sessions.
3

Optionally pin a repository

For an agent that only ever works in one repository, add ?repo= to its endpoint, for example https://api.graphify.com/mcp?repo=acme/api. It can then leave out the repository in each call.
4

Commit one instruction block to every repository

Add this to AGENTS.md (read by Codex and many other agents) and CLAUDE.md (read by Claude Code) in each repository:
AGENTS.md

​
How it works

Graphify keeps the graph and memory in the workspace, not in any one agent. Every agent connected to that workspace reads the same index of your default branches and the same kept memories. A decision one agent saves with remember starts as a suggestion. Other agents may already see it, marked as unverified. Once you keep it in Memory, it’s a reviewed memory every agent gets from recall and memories_about. The agents don’t talk to each other through Graphify, and Graphify doesn’t divide up work between them. It gives them a shared, current picture of the code and of what you’ve decided.

​
Verify it worked

  • Ask two different agents the short-version prompt. They report the same workspace and repositories.
  • Keep one memory in Memory, then ask a different agent memories_about on that file. It returns the memory.

​
Troubleshooting

  • One agent sees different repositories. It’s in another workspace. Check with list_workspaces and switch with set_workspace.
  • A saved fact shows up as unverified, or not at all. It’s still a suggestion. Keep it in Memory. See Memory.
  • Answers look out of date. The graph follows each repository’s default branch. Check freshness with graph_stats.

​
Next steps

Try it in Graphify

We build and host the graph for you. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

Memory

What agents remember, and how it’s reviewed.

What your agent can do

Every hosted tool, with a prompt for each.