[ 001 ]CONTEXT AMNESIA
Every session starts cold.
Every new tab or agent session flushes previous instructions. You restate preferred languages, design rules, and project patterns over and over.
WEBMCP PROTOCOLCROSS-SITE RECALLZERO REDUNDANT PROMPTING100% USER GOVERNEDSTRUCTURED CONTEXTNO CLOUD VENDOR LOCK-INWEBMCP PROTOCOLCROSS-SITE RECALLZERO REDUNDANT PROMPTING100% USER GOVERNEDSTRUCTURED CONTEXTNO CLOUD VENDOR LOCK-IN
THE PROBLEM
Agents don't have memory. And you're stuck repeating yourself.
Context dies at the tab boundary. The user becomes the integration layer, re-typing the same four facts into every tool they touch.
LAT: 37.7749
LON: -122.4194
SCAN: AGENT VECTORS
▲ CONTEXT VOID DETECTED04 FAULTS
[ 002 ]WALLED SILOS
Memory trapped in proprietary clouds.
Cloud assistants lock memory into closed silos. Independent web apps cannot collaborate on shared user context without brittle custom integrations.
[ 003 ]REDUNDANT PROMPTING
They meter your patience.
Instead of creating, you spend the first three minutes of every session re-configuring a basic environment the agent already learned once.
[ 004 ]ZERO GOVERNANCE
Opaque context, no human control.
Traditional agents collect context silently: no visible audit trail, no source lineage, and no obvious way to purge what you never wanted kept.
INTRODUCING TETHER
Shared context. Local control. Engineered for agents.
WebMCP gives each site a way to expose real capabilities to an agent. Tether is the persistence layer those capabilities read from and write to.
[ 01 ]
Participating sites
DesignLab and DevForge each register their own WebMCP tools with the page's model context. An agent discovers them like any other page capability.
WebMCP tool call
[ 02 ]
Tether persistence layer
Next.js route handlers validate every input with Zod and write structured memories to Postgres. One contract, any number of sites.
inspect / delete
[ 03 ]
Human governance plane
The user sees every memory, its source lineage, and its confidence. They can delete any of it permanently, at any time.
To be precise: WebMCP does not carry memory between sites on its own. It is the interface that lets each page hand an agent real tools. Tether is the shared backplane those tools read from and write to, which is what makes context earned on one site useful on the next.
Tool discovery
In-page
Agents read tools straight off the page's model context, with no broker hop.
Human control
100%
Every memory is inspectable and permanently deletable by the user.
Re-prompting
$0
Context taught once is reused, not re-typed and re-tokenised per site.
Scope
Session
Memories live in one opaque first-party session. No accounts, no PII.
CAPABILITIES
What the memory layer actually guarantees.
Six properties that separate a shared context layer from an assistant's private chat history.
Multi-site interoperability
Context written by one participating WebMCP site is readable by the next through a single shared contract, with no bespoke integration per pair of sites.
WebMCP native protocol
Tools are registered on the page's own model context. Agents discover real site capabilities instead of scraping a DOM that was never meant for them.
Full human sovereignty
Every memory shows its source, the tool that wrote it, and when. One click deletes it everywhere, permanently, with no shadow copy left behind.
Structured semantic storage
Category, tags, and a confidence score, not an undifferentiated text dump. Structure is what makes retrieval explainable rather than magical.
Sandboxed privacy model
Memories are scoped to one browser session via an opaque first-party cookie. No accounts, no PII, no third-party telemetry.
In-page tool execution
Tools run in the browser against a same-origin API. There is no extension to install and no external agent broker in the path.
FAQ
Frequently asked questions.
Tether is a shared persistence layer for the agent-native web. It lets WebMCP-enabled websites save, retrieve, update, and delete structured user context so people stop re-prompting the same four facts into every tool they open.