Project memory you can inspect.

01. Connect your project sources

Start with a repository and its available documentation. Episyne records source references and relevant project changes, making the origin of retrieved context easier to inspect.

02. Separate current guidance from history

A previous decision may have been replaced. Two documents may disagree. Episyne distinguishes current, historical and unresolved information so you can check what applies before continuing.

03. Resume with context

Use the CLI or MCP integration to retrieve project context for a task. Review the referenced evidence, open questions and the next recorded step before relying on an agent response.

An illustrative example

MarketCore is a fictional project used to show how an accepted settlement decision can replace older guidance. The website illustration uses synthetic records.

Separately, a synthetic Git project was published with the Episyne CLI and read through a real worker and MCP workflow. This is a technical verification of those paths, not a claim that the website illustration was generated from that run.

Frequently asked questions

What is Episyne?

Episyne is a developer tool for retaining inspectable project context, including decisions, supporting sources, and unresolved questions, across coding sessions and agent handoffs.

How is Episyne different from chat memory?

Instead of relying on a conversation summary alone, Episyne relates project guidance to source references and distinguishes current decisions from superseded or conflicting information.

Does Episyne replace my coding agent or language model?

No. Episyne supplies project context to supported CLI and MCP workflows. Your agent and its model remain separate tools, and compatibility depends on the integration you use.

How do I get access?

Episyne is preparing a Founding Beta with invitation-based access. A request for access does not automatically create an account or a paid subscription.