Your data & access

The source of truth

This guide covers the Wayform product. The website’s early access requests use a separate database and email notifications. Read about the access form’s data handling.

Plans and recorded decisions are stored in your space’s append-only ledger on the hosted Wayform service. Entries are never edited in place; corrections are new entries that supersede old ones, so the full history stays readable.

You can optionally mirror the ledger to a private GitHub repository in your account. The mirror receives each new entry as a commit, so you keep a git copy you can inspect and audit. The ledger stays the source of truth.

The hosted service also maintains a retrieval index, including indexed facts and embeddings, so it can find relevant context.

GitHub permissions

A space doesn’t need a GitHub repository. If you set up a mirror, select only the private mirror repo when you install the GitHub App; it gets contents access to exactly that repo.

Recording linked PR events from a product repo is a separate integration setup. Don’t assume access to the memory repo also grants access to your product repo. Review the GitHub App’s requested permissions and selected repositories during installation.

New spaces currently require the GitHub owner or organization to be approved. Members of an active space sign in with their GitHub identity.

Authentication

The desktop app signs in with GitHub through OAuth and keeps its credential in the macOS credential store, outside the app’s web view. Coding clients connect to the hosted MCP service using OAuth. Terminal hook authentication uses the CLI login and the OS credential store. Don’t put access tokens in project files, commands committed to Git, or shared documents.

Local agents and chats

Your coding agent runs in your environment, including builds started from the app, which run in a separate worktree on your machine. Chat and build transcripts stay in the app’s local data directory; plans you save and decisions you record enter the shared service and memory repo.

Your chosen coding agent and model provider have their own data handling. Local execution of the agent process does not mean its model runs locally.

Team access

An admin can invite a teammate by GitHub username or revoke their space membership. Each member uses their own OAuth login; nobody needs to share an API key.

The current product supports one Wayform space per GitHub user. A space can hold multiple projects. Project names select which plans and context your agent is using.

Review connected sessions

Ask your agent:

List my Wayform sessions.

The session list shows connected clients and identifies the current session. To disconnect one, ask the agent to revoke its session ID. Revocation is scoped to your own account; removing a teammate is an admin action.

Know the boundaries

• Members’ recorded content can enter teammates’ agent sessions. Treat space membership as a trust boundary.
• The guard can surface contradictions with recorded decisions. It is not a security sandbox.
• Auto mode lets the agent’s own reviewer approve routine actions. Wayform’s deny rules apply first, but a reviewer is not a security boundary.
• Hooks fail open on runtime errors. Verify the setup with diagnostics instead of relying on silence.
• The current app build is unsigned. Obtain it through your approved access setup and verify its source.

This page describes product behavior. It is not a certification or a promise of zero data processing.