Shared memory for Codex

What carries into a new Codex session?

Wayform makes saved project decisions and plans available to Codex through MCP. Supported startup hooks bring context into a fresh session, and Codex can search for decisions while planning or building.

It shares the recorded work with other connected teammates and agents. It does not restore a full conversation or replace AGENTS.md.

Connect Codex

Start with the quickstart to create or join an approved Wayform space. Run these commands from your product repository:

wayform init --remote --clients codex
wayform login
codex mcp login wayform
wayform doctor

Setup writes project-scoped MCP configuration and supported hooks. Complete authentication and trust the project when prompted. Start a new Codex session afterward; a session opened before login may not load the connection.

Check the memory round-trip

Use a small, deliberate decision. This example is illustrative:

Save in Wayform: team invitations must use our existing GitHub login because we want one identity system.

Check that the decision was recorded against the correct project. Open a fresh session, then ask:

Search Wayform for our team invitation decision. Explain the approach and the reason before proposing changes.

The retrieved record should contain both. If it doesn’t, check authentication and the project name.

Build from a saved plan

After making and activating a plan, launch it with:

wayform build 12 --client codex

Replace 12 with your actual plan number. Codex runs in your environment. Learn the plan workflow.

If a supported action conflicts with a decision, the guard can surface it for your review. It can also flag something that does not apply. Review the cited decision before allowing an exception. The guard is not a security sandbox, and runtime hook failures can leave an action unchecked.

Keep stable repository instructions in AGENTS.md. Use Wayform for the plans and decisions your team wants to reuse. Compare the two.