Put your product in Waymode.
Let people and their AI agents use your product.
Your product. Now in Waymode.
One app, with more ways in. Explore a connection.
Your app does it. The UI comes to you.“Open settings here.”
Real controls, inside chat.
A cursor guides the way. Bring your agent.Use your app from a connected assistant or computer-use workflow.MCP + MCP Apps Planned
Your actions. Your permissions. Your state. Waymode connects the paths.
A little more under the hood.
Already agentic or just getting started. Waymode connects AI to the actions and interfaces you already own.
What stays yours?
Your handlers, state, permissions, and choice of decision model. Waymode selects from connected actions and checks scope and freshness. Your app still authorizes each operation and verifies saved changes.
What happens when I add a feature?
A new control enters the connected web surface’s next snapshot. Backend actions use your connected contracts. Those features need no matching feature-specific model tool. Hidden functions and unconnected APIs still need integration.
How do live views and guidance work?
Connect an app view so its real controls can appear in chat. Waymode can also navigate the connected interface and guide a user with a cursor. Both use the app’s existing behavior; security prompts and actions that need the user remain in their hands.
What about external agents and MCP?
Connect an external agent through an authenticated transport to discover supported actions and read results. It can use those actions alongside its browser controls, without navigating menus for each exposed task. Read the integration contract.
The remote adapter is available. Ready-made MCP, WebMCP, and desktop controllers are not included. MCP and MCP Apps are future integration paths, not shipped support.
What can I use today?
The open-source SDK supports same-document web apps and React DOM hosts. Dedicated Next.js, TanStack Start, React Native, and native adapters are planned. Check the current setup instructions.
Where is the proof?
The live showcase’s Activity tab shows its calls and results. The eval contract explains how claims must be backed by retained runs. Unit tests alone do not prove model accuracy or a speed advantage.
Now put your product in Waymode.
Copy this prompt into Codex, Claude Code, Cursor, or your coding agent.
Read the install prompt
Install Waymode in this repository. Start by reading the source and installation instructions at https://github.com/mossburgh/waymode. Detect every client and server boundary in this product. Connect Waymode to the product’s existing actions, permissions, and interface. When a safe action is not exposed, add the smallest reusable primitive that makes it available without copying business logic. Run Waymode’s setup checks and self-driving evals, keep working until they pass, then summarize what users can now ask the product to do.