wayform
Now in private beta

Wayform

Shared planning memory for AI teams

One teammate makes a decision in Claude. It's already loaded in everyone else's Cursor, Codex, or ChatGPT — automatically, at session start, with nobody pasting anything.

No spam. One email when the beta opens.
How it works

Maya decided in Claude. Chris opened Cursor.
The decision was already there.

One decision, captured once, injected everywhere — across different people and different tools, with nobody pasting anything.

Claude Code CAPTURE
M Maya
Need a store for the app — Postgres feels heavy for an MVP.
SQLite is zero-config, a single file, and plenty under ~10k users. Postgres adds ops you don't need yet.
Let's use SQLite — zero-config, single file.
write_context MCP · space/core
✓committed to space/core · @maya · just now
commit
space/core append-only
a1f2c9 decision: use SQLite for store
Maya committed · 2h ago
7bd0e1 context: MVP target ~10k users
decision
Use SQLite for the store — zero-config, single file, good enough until 10k users.
author Maya
project core
your private git repo · you own the data
inject
Cursor Nothing pasted
A Chris · fresh session
Team context · loaded at session start
Use SQLite for the store — zero-config, single file.
M Maya · space/core · 2h ago
What are we using for the data store on this?
SQLite — Maya settled that 2h ago. Zero-config, single file, fine to ~10k users. Want me to scaffold the store?
→ 0 copy-paste · injected automatically
Same decision, byte-identical in any MCP client — Cursor, Codex, ChatGPT.
Works with any MCP tool

One memory across every tool your team already uses.

Wayform speaks the Model Context Protocol. Anything that speaks MCP — coding agents, design tools, chat assistants — reads and writes the same byte-identical context. No adapters, no lock-in.

Coding
Claude Code
Coding
Cursor
Coding
Codex
Chat
ChatGPT
Chat
Poke MCP
Design
Figma MCP
Docs
Notion MCP
Any client
MCP-native
Why Wayform
Curated, git-backed, and yours. Not a firehose of tokens — a record of what your team actually decided.
01 · MULTIPLAYER
One store per team
Everyone shares the same context. Attribution comes straight from git commit authorship — you always know who decided what, and when.
02 · NEUTRAL
No vendor lock-in
The same decisions surface byte-identical in every MCP client. Switch tools freely; your team's memory travels with you.
03 · OWNERSHIP
It's your git repo
The store is a private git repo in your own account. Git is the audit trail and the merge engine — no black box, no export button needed.

Give your team
one shared memory.

Early access to the private beta. Spaces open now.

No spam. One email when the beta opens.