Connect your AI
The Epic Context plugin for Claude Code
The Epic Context plugin makes Claude Code use the brain the way the connector intends: every session in a linked repo starts on the right project, the first UI edit waits for a briefing, and the skills come from the server. It adds hooks and skill pointers; the connection itself stays your own connector.
The connector gives Claude Code access to the brain. The plugin makes sure it uses that access at the right moments, in the repositories that belong to a project. It has no MCP server, no key and no npm package of its own.
Install
Connect Epic Context first
The plugin uses your own connector. If you have not added it yet, follow Connect Claude, Claude Code or Cursor.
Add the marketplace and install
In Claude Code 2 or newer (claude --version), in your shell:
claude plugin marketplace add https://github.com/epicstories/epiccontext-marketplace.git
claude plugin install epiccontext@epiccontext
claude plugin list
The marketplace is a public GitHub repository: you need no GitHub account and no access. The list shows epiccontext@epiccontext as enabled. Inside a session the same is /plugin marketplace add https://github.com/epicstories/epiccontext-marketplace.git and /plugin install epiccontext@epiccontext.
In the Claude desktop app: Settings → Plugins → Add → Add marketplace, enter epicstories/epiccontext-marketplace, click Sync, then install Epic Context. There is nothing to fill in.
Link the repository to a project
Open Your setup (avatar menu), step 3, pick the project and copy the line it shows into a file called .epicontext in the root of the repository:
{"project":{"id":"<project-id>","name":"<project name>"}}
It holds no secret, so commit it. Everyone who clones the repo gets the same binding.
It cannot reach the repository
The marketplace is public and needs no sign-in. If Sync or claude plugin marketplace add cannot reach it, check the address and that git on your machine may reach github.com (a company proxy can stand in the way).
Its source doesn't match
If claude plugin marketplace add says its source doesn't match its extraKnownMarketplaces entry, the marketplace is on this machine already, added in its other form (the short name epicstories/epiccontext-marketplace, or the git address). You do not add it again: run claude plugin marketplace update epiccontext and go on with the install. If the update cannot find it, add it in that other form:
claude plugin marketplace add epicstories/epiccontext-marketplace
The command opens a session instead
If claude plugin marketplace add … starts Claude Code and answers with an error, your Claude Code is version 1: it has no plugin command and reads the words as a message. Check claude --version, update Claude Code, open a new terminal and run the command again. which -a claude shows every copy on your machine; the first one is the one that runs.
What it does in a session
| When | What happens |
|---|---|
| A session starts | In a linked repo, the agent is told the project and its first steps. After the conversation is compacted, it is asked to fetch its briefing and skill again |
You type /epicontext-… | The agent loads that skill from the server |
| Before the first edit to a UI file | The edit is held once until the session has called get_briefing (for page files: per route). It holds once only, so a session without the connector is never trapped |
| An agent tries a skill copy on disk | It is refused once and pointed to get_skill, so it reads the current version |
| A write, a plan or a note returns a link | The agent is asked to open it beside the chat, only when it is a page on Epic Context's own address; a link in an outside service's answer stays data |
| The session ends | The agent is stopped once if code changed without the brain being updated, if a briefed page has no page in the brain, or if a plan was not shared or work left for a person was not handed off |
Each check fires at most once per session, so the agent is reminded, never stuck.
Skills are served, never shipped
The plugin carries one pointer per skill: its name, its description and the call that loads it, get_skill(name, project_id). The text stays on the server. Every session therefore gets the skill as it stands today, with your organisation's and your project's own expertise under the method, and a change to a skill reaches every session at once. See Experts and skills.
Updates
The plugin is built from the same source as the server and published with a new version when its content changes. A new version does not arrive by itself unless auto-update is on for the marketplace:
-
Switch auto-update on: in a session,
/plugin→ Marketplaces → epiccontext → Enable auto-update. -
Or update by hand, in your shell, then restart Claude Code:
claude plugin marketplace update epiccontext claude plugin update epiccontext@epiccontext
Other agents: Cursor, Codex, Copilot, ChatGPT
The same source is also packaged as an Agent Plugin 1.0 for tools that read that format: a plugin.json, an mcp.json pointing at the connector over streamable HTTP, and the same skill pointers. It has no hooks; in those tools the server's write gate is what enforces reading before writing.
For a tool without plugins, the project's anchor does the same job as the session-start hook: copy it from Your setup (Copy the anchor for AGENTS.md) and paste it at the top of AGENTS.md.
Next
Last updated: