The control plane for teams of humans and agentsAgents are good.They could be better.

Wayform for macOS
Claude Code · Cursor · Codex
See how it works

Wayform gives your agent the plan, the decisions, and the reasons behind them.

Works with
your coding agent.
Claude Code
Cursor
Codex
See how they connect ↗

A plan your agent
can actually follow.

Plan in the macOS app. Build with your own coding agent. Check the result against the plan.

Here’s what that looks like.Example project · pick a view
Wayform / acme⌘ K
Plans / #12◌ Active
PLAN #12 · V3
Invite your team.
Keep everyone in the loop.

Add team invitations without introducing a second identity system.

↳
INHERITED DECISION

Use GitHub identity. No separate accounts.

Settled by Chris · carries into this plan
The approach

Extend the existing space membership flow. Keep access scoped to the team’s space.

✓ Define the invitation flow✓ Reuse GitHub authentication Verify access boundaries

Your agent already knows what you ruled out.

Your agent reads the repo and the decisions behind it before writing the plan.

Illustrative content · based on the Wayform workflow

New chat.
Same team decisions.

A decision made with one agent carries into your teammates’ sessions. They build on what’s settled instead of debating it all over again.

MayaClaude Code · Friday

“Use GitHub login. We don’t want a second auth system to maintain.”

↳ Decision + reason saved for the team
WayformShared team memory
ChrisCodex · Monday, fresh session
Chris asks“Add team invitations.”

“Your team already chose GitHub login. I’ll extend that flow.”

↳ Uses Maya’s decision. Doesn’t reopen it.
Illustrative example: two teammates, two agents, one shared decision. Nothing to paste or re-explain.
GET IT BUILT

Build with the agent
you already use.

Keep the coding agent and environment you like. Launch the plan in Claude Code, Cursor, or Codex, with each task briefed by the team’s decisions.

When an action conflicts with a recorded decision, the guard brings it back to you.

Build in your own tools ↗
#12 / Team invitations✓ Read inherited decisions✓ Inspect existing auth flow↳ Propose new account table…
!
A DECISION NEEDS YOUR CALL

We already chose GitHub identity.

This action introduces a separate account system. Continue, or keep the existing approach?

Keep existing approachReview decision ↗
A GUARDRAIL, WITH YOU IN CONTROL.
REMEMBER WHAT CHANGED

Ship it.
Remember why it works.

Have your agent check the diff against the plan before opening a PR. When a linked PR merges, the plan ships and its decisions become shared context.

The next plan, next session, and next teammate start a little further ahead.

How the loop closes ↗
✓PLAN #12 SHIPPEDmerged
WHAT WE DECIDED

One identity system.

Reuse GitHub authentication because team access should extend what’s already there.

A decision, with its “because”.
THE NEXT PLAN

Already knows why.

FOR TEAMS

One control plane
for humans and agents.

Every teammate’s agent plans from the same decisions, builds under the same guard, and leaves the next session a little further ahead.

YOUR TOOLS. YOUR HISTORY.

It’s your work.
Keep it that way.

Your plans and decisions live in an append-only ledger, mirrored to a private GitHub repo if you want a git copy. Your coding agent runs on your machine. Chats and builds stay there too.

Read about data & access ↗
One place to think
A macOS app to plan, build, and review your agents’ work.
Bring your own agent
Claude Code, Cursor, or Codex. Use your existing setup.
A history you own
Versioned, append-only plans and decisions, with an optional GitHub mirror.
Start solo. Add your team.
The same shared context, across people and coding sessions.

For macOS. With the agents you already use.

Read the docs ↗
Get early access