A teammate handoff

How does a decision reach another teammate’s agent?

Both agents connect to the same Wayform space and project. One records a decision; the other can retrieve it. Supported startup hooks bring context into new sessions, so the handoff doesn’t depend on copying the original chat.

The following is an illustrative walkthrough, not a customer result.

Maya settles the auth decision

Maya is working in Claude Code. The team has agreed to reuse GitHub login, so she asks:

Record this in Wayform: use GitHub identity for team invitations. We don’t want a second auth system to maintain.

She checks the saved record and project. Now the reason is available alongside the choice. More on recording decisions.

Jamie connects Cursor

A space admin invites Jamie’s GitHub username. Jamie signs in with their own account and selects the same Wayform project. No shared credentials.

From the product repo, after completing the quickstart:

wayform init --remote --clients cursor
wayform login
agent mcp login wayform
wayform doctor

Jamie trusts the workspace and approves the Wayform connection in Cursor, then opens a fresh session. If Jamie uses Codex instead, follow the Codex setup.

The next task starts with the decision

Jamie asks:

We’re adding team invitations. Search Wayform for the decisions that apply, then propose a plan.

The agent should retrieve Maya’s decision and plan around the existing login flow. Check the retrieved reason before building. Jamie can review the saved plan in the desktop app.

The useful outcome is specific: the next agent can spend its time on invitation behavior instead of asking the team to choose an identity system again.

If the decision needs to change

Shared memory should not make an old choice permanent. If the requirements have changed, ask the agent to find the old decision and explicitly supersede it with the new choice and reason.

Different project names, missing membership, or an unauthenticated client will break the handoff. Use troubleshooting to check those first. Hook support also varies by client; ordinary MCP access alone does not provide every integration feature.

See Your data & access for what enters shared memory and who can access it.