What still holds?
Distinguish accepted decisions from guidance that has been replaced.
PROJECT CONTEXT FOR CODING AGENTS · FOUNDING BETA
Your project changed. Does your agent know what still holds?
Episyne is a developer tool that keeps project decisions, supporting evidence, and unresolved questions traceable across coding-agent sessions and handoffs.
Episyne helps you carry project decisions and their evidence across coding sessions, agents, and handoffs — so you can resume work knowing what still applies.
Codex and OpenCode setup paths documented
Exploring with your team? Apply for the founding team pilot. No access is granted automatically.
Episyne / MarketCoreILLUSTRATIVE UI · DEMO DATA
WHERE TO RESUME
Prevent duplicate payouts when sell orders retry.
ADR-009 is documented. Concurrent retry testing remains pending; interrupted responses are unverified.
Next recorded stepRun concurrent sell retries with a dropped response.
Inspect handoff
THE PROBLEM ISN’T JUST MEMORY
Context needs a reason to be trusted.
Where did it come from?
Inspect the evidence behind a project-context claim.
What needs review?
Surface unresolved conflicts instead of silently treating the newest note as truth.
01 · ONE CLEAR PROJECT STATE
Keep the decision. Leave the outdated advice behind.
Pick up a project after a week away. This fictional MarketCore scenario shows what should be inspected before trusting an agent’s context.
Product-interface illustration with synthetic demo data. The separately verified CLI/MCP results below did not generate this UI scenario.
Decisions / MarketCoreILLUSTRATIVE UI
Decisions
Recorded directions and changes, with their evidence.
AllCurrentPast
PostgreSQL order ledger is authoritative for sell-order settlement.Workspace · 1 source
CurrentRedis-first settlement was replaced by ADR-009.Workspace · 1 source
Superseded2 decision records · open questions belong in Review
Which direction applies?
ADR-009 records PostgreSQL as the settlement authority. Redis-first is historical guidance.
Where is the evidence?
Inspect the accepted source. Keep questions and conflicting documentation separate from applicable decisions.
Where should work resume?
Next: test concurrent retries after a dropped response. The test has not been executed in this synthetic project.
REAL LABORATORY VERIFICATION
Not just a UI concept.
A separate synthetic Git project was published using the CLI, certified READY by the real worker, then queried with six MCP read tools.
How we label evidence →MARKETCORE / ISOLATED TESTREDACTED RESULT
$ episyne init --new-workspace "MarketCore Synthetic Demo"
PASS · publication accepted · 4849 ms
$ episyne ask "Where is atomic settlement documented?"
PASS · 5 references · docs/adr/009-atomic-order-settlement.md
$ MCP read verification
PASS · read-model READY · 6/6 callsSanitized test summary, not verbatim terminal output. Successful reads do not imply that the illustrative decisions or handoffs were generated automatically.
02 · WHEN SOURCES DISAGREE
Memory is useful. Knowing when guidance is stale is better.
The old runbook updates Redis quotes before committing a sale. ADR-009 records the opposite order. The discrepancy should stay visible until reviewed.
A focused excerpt, not another full dashboard.
One source says
The older runbook updates Redis quotes before the order commits.
Another source says
ADR-009 requires a PostgreSQL commit before publishing new quotes.
03 · IS THIS YOUR PROBLEM?
Useful when a project has a history worth checking.
Episyne is meant for long-running development work, not every chat or every repo.
Decisions have changed, but their old sources remain.
You use coding agents, maintain architectural decisions, or need to inspect contradictions across sessions. A verifiable state may help.
Explore the decision flow →A simple project with a reliable context file.
If a small AGENTS.md, project README, or manual handoff works consistently, start there. Episyne is not required for every workflow.
04 · START WITH A PROJECT
Start in your existing repository.
Bind your repository, inspect its initial state, and verify the evidence before trusting agent context. A successful setup is not the same as proven value.
Setup paths includedCodexOpenCode
Client compatibility depends on the installed CLI, MCP and agent versions. Check the current integration instructions before use; this page does not certify every client release.
View integration notes →Use another agent client? Tell us which one. A client is listed only after we validate it end to end.
episyne loginAuthorize this installation.cd your-projectOpen the repository you want to use.episyne initBind the project.
05 · TRUST BY DESIGN
Know what crosses the boundary — and who gets the last word.
References first.
Full-repository cloud upload is off by default.
No server-side LLM required for the core.
The part that decides what still applies does not require server-side model inference.
You remain the authority.
An agent can propose. It does not silently turn its own output into an accepted project decision.
06 · JOIN THE FOUNDING BETA
One shared context. Two ways to start.
We are inviting early developers and engineering teams to evaluate Episyne while release certification continues. Applying does not create an account or require payment.
Stop rebuilding context every session.
Bring a repository and a real instance of outdated or missing project guidance. Tell us what your coding agent failed to remember.
- Early access by invitation
- Evidence and source inspection
- Feedback that shapes the beta
Make handoffs easier to trust.
Explore a guided pilot for a small team with real decisions, blockers, and conflicting documentation. Teams Preview is still under certification.
- Review technical fit together
- Discuss a controlled pilot
- Agree on scope before any commitment
Comparing approaches? Read our comparisons and frequently asked questions.
Already comparing approaches? Read our method, integration status, and data boundaries before applying.