Project continuity for coding agents
A fresh agent can read the repository. Give it the decisions, constraints and investigations that explain the code before it starts changing it.
Premium includes 2,000 MCP operations and 25,000 hosted-intelligence credits per month.
Project notes / ADRs / research / decisions
The history behind the repository
Phasoric durable context
Only the knowledge you authorize
Codex / Claude Code / Cursor / Copilot
Retrieve context → implement with client permissions
Reviewed decision / write-back
Approve the note → better context for the next agent
Ask for context before action
“Read the implementation brief and related decisions in my Phasoric Vault. Summarize the constraints and rejected approaches with source paths before changing code.”
The brief, the repository and the agent stay distinct. Phasoric supplies authorized knowledge; your coding agent uses its own workspace permissions to implement the change.
Save architecture decisions, implementation briefs, rejected approaches, incident history, requirements, constraints, deployment decisions and known technical debt.
Ask the agent to find the relevant records and previous investigations. Check the source paths and unresolved questions before accepting a plan.
After implementation, review a proposed decision note and approve its write-back separately. The next agent can retrieve that updated record.
From our own work · September 2026
We asked Codex to read a Phasoric Vault brief about persistent MCP connections. It retrieved the plan through Phasoric, investigated the OAuth flow, and implemented the fix in the repository. The reasoning traveled with the task.
An existing Markdown plan supplied the problem, constraints, and acceptance criteria.
Codex used the brief to guide the code changes and tests in the project.
The fix was merged into develop after approval, with release validation still explicit.
Explore the workflow
Read the context. Do the work. Save the reasoning for next time.
Recover the rationale
Keep access tokens short-lived. Use rotating refresh tokens so an authorized agent can renew access silently. Keep vault-provider credentials behind Phasoric.
Source: Persistent MCP OAuth brief · requirements and constraints
The agent reads the original plan and its reasoning before proposing a change.
Use the client’s own workflow
Connect Phasoric on the host where the task runs. In a fresh task, ask Codex to read the brief, name its constraints and inspect the repository before editing. After review, propose the outcome as a separate decision-note update.
Adding the URL and authenticating are separate steps. MCP knowledge access grants no repository or deployment authority.
Set up CodexUse the documented remote HTTP setup, then inspect and authenticate the connection with /mcp. Try: “Find the ADR for this subsystem. Which approach did we reject, and why? Cite the source before suggesting the same change again.”
This is a suggested workflow, not a recorded Phasoric interoperability test. Claude’s remote connector and Claude Code use different setup paths.
Set up Claude CodeDurable context. Deliberate access.
Phasoric exposes the knowledge you authorize. It does not silently ingest every conversation or automatically remember everything your agents do.
Inspect the MCP boundariesHosted MCP reaches explicitly mapped Phasoric Hosted, Dropbox, Google Drive or GitHub vaults. Local-only vaults and device-encrypted remote bodies remain unavailable.
Ask for the note path, evidence and limits of the answer. Your Markdown remains portable across tools.
Review a proposed note change before application. Write permission, current-content checks and duplicate-request safeguards still apply.
Documented client setup
An authenticated Vault read was verified in Codex. The other guides describe documented setup paths; client plans, versions and workspace policies determine availability. They do not establish Phasoric interoperability for every client version.
Prepare your vault and verify a first readOpenClaw, Hermes Agent and Grok document remote MCP connection paths. These guides map those instructions to Phasoric; authenticated interoperability has not been verified for these clients.
No. Repository instructions still guide work in that checkout. Phasoric supplies the authorized project history, research and decisions that may live outside it. Ask the agent to retrieve that context explicitly.
No. Phasoric does not silently ingest agent conversations or repository changes. Save the useful outcome and rationale as a reviewed note if you want a future task to retrieve it.
An authenticated Phasoric Vault read supplied the persistent-MCP brief used in our real Codex investigation and implementation. This is evidence for that workflow, not proof of every client version or unattended deployment.
Start with one project
Keep the brief, recover the evidence and save the reviewed decision. Choose how you want to use that context.
Connect the AI tools you already use to your authorized Phasoric knowledge. Hosted MCP starts with Premium.
$14.99/month includes 2,000 MCP operations and 25,000 hosted-intelligence credits each month. Higher plans increase limits and features.
Connect my AI toolsNo MCP setup required. Ask Phasoric directly using hosted intelligence with bounded relevant source context.
Eligible Free hosted accounts can buy 50,000 credits for $5.99. Usage is metered; a credit pack does not enable MCP.
Try hosted intelligence