Decisions & shared context

How does Wayform share memory between coding agents?

Wayform stores your team’s plans and decisions in a private GitHub repository. Supported coding agents connect to the same project through MCP. Session-start hooks bring decisions into fresh sessions, and agents can search the shared memory while they work.

The saved context is the decision and its reason. It is not a copy of every chat. A teammate using a different supported agent can build on that decision without having to paste the original conversation.

For client setup, see Connect Claude Code, Cursor, and Codex. For storage and access boundaries, see Your data & access.

Record the why

Ask your agent to save a decision in ordinary language:

Remember that we chose GitHub identity because we want team access to extend the existing authentication flow.

Be explicit about what was settled and why. Record decisions you want future work to respect, rather than every message or intermediate idea. Your agent can use write_context to add durable context or a settled decision.

Context across sessions

Supported session-start hooks bring project decisions and relevant activity into the agent’s context. Before a new plan, plan_brief retrieves the decisions that bind the task.

The agent can also search memory before revisiting an old choice, asking you to explain something again, or recommending work that may already be done.

Your teammates’ agents can use the same plans and decision history, even when they use different coding clients.

Change a decision deliberately

Teams change their minds. Ask the agent to find the old decision and record its replacement with a link to the fact being superseded.

We’re replacing the temporary invitation flow with expiring invitations because the team now needs explicit revocation. Find and supersede the earlier decision.

This preserves the history while keeping an obsolete decision out of current briefings. A correction should replace the old fact, rather than creating a second, contradictory version without a link.

When the guard intervenes

Before a supported mutating tool call, the guard checks the proposed action against current decisions. A contradiction brings the recorded decision back to you.

You can keep the decision, revise the proposed action, or explicitly authorize an exception. An exception applies to that decision for that member for a short window; it is not a permanent rewrite of team policy.

The guard is a useful check, not an exhaustive enforcement system. Client support and service availability affect what it can catch.

Learn from shipped work

Shipping a plan records the decisions it produced so future tasks benefit from the result. With the product-repo GitHub integration configured, linked PRs can advance plan state and capture the result at merge.

The next plan should inherit useful conclusions, not a transcript of every implementation step.

Trust the people in your space

What a member writes can inform every member’s agent. Invite people you trust to shape the team’s shared context. Read about access and data.