Identify the client.
Check CLI, API and MCP versions and whether authentication works in that environment.
DOCUMENTED WORKFLOWS · BETA
Keep the agent. Inspect the context.
Episyne is designed as a separate layer of project state and evidence. It does not claim universal support across coding agents.
Documented setup candidates include Codex and OpenCode. We only label a client as supported once that CLI/MCP/client combination has passed a release-specific end-to-end test.
HOW TO EVALUATE AN INTEGRATION
Connection is the beginning. Evidence is the test.
Retrieve context.
Exercise a representative task and inspect the state, source references and error behavior.
Review currentness.
Confirm relevant decisions and superseded guidance before describing that client as validated.
Compatibility status is release-specific. A successful connection alone is not a certified integration.
START WITH YOUR REPOSITORY
Initial project setup
episyne login
cd your-project
episyne initThese commands establish the starting point.
The CLI binds and processes your project. A successful initialization is not proof of a useful retrieved decision; inspect the actual evidence and states in a compatible client.
We do not claim that initializing the repository automatically imports the full Git history or ensures every note becomes an accepted decision.
How we verify claims →CLIENTS UNDER DOCUMENTED TEST COVERAGE
What to check before integrating
Codex workflow
Confirm CLI and MCP versions, authentication, read-path behavior, permissions and evidence visibility in the real Codex environment. This page does not certify a specific Codex release.
OpenCode workflow
Apply the same end-to-end compatibility checks. Validate the first evidence-backed response instead of relying on a connection-success indicator alone.
Claude Code, Cursor and other agents are not described as validated integrations by this static candidate. We only publish integration claims after end-to-end certification.
MISSING A CLIENT?
Tell us your workflow.
If you use another coding agent, we can consider it for future compatibility testing. No unsupported integration is promised.
Request compatibility details
For verified setup instructions and version-specific status, contact the team.
Share your workflow →