CSE Roadmap

Common tier · about 6 hours · 14 parts

Part 5 of 14 · 3 min read

Form mode is for data; URL mode is for anything that must never touch the client

A password typed into a form on the client's screen has already passed through the client, its logs, and possibly the model, before the server ever sees it.

Think of filling in your own bank PIN on a merchant's own keypad, versus being handed a separate, dedicated terminal for it. The first keeps the sensitive step inside a system you do not control. The second keeps it out entirely.

In plain words: form mode asks for structured data (a confirmation, a choice, a date) through a flat schema the client can render and validate. URL mode sends the person to a page outside the client for anything that must bypass the client altogether: a sign-in, a payment, a secret. Because that page is reached by a link, the server must also verify that the person who completes the page is the same person who started the request, or a trick message can connect one person's account to someone else's data.

A worked example. Screening seven candidate addresses: a plain https://mcp.example.com/connect?id=lnk1 link passes; a plain http:// link is blocked; a user-name trick (https://[email protected]/connect, whose real host is evil.example) is blocked; a punycode domain is allowed but flagged; a javascript: scheme is blocked outright. Separately, when Alice starts a calendar connection and Bob is tricked into opening her link and signing in with his own account, a server with no identity check accepts Bob's sign-in and leaves Alice connected to bob@calendar. The same server with the check in place refuses Bob ("this link was issued to someone else"), and Alice's connection stays untouched.

The key lines. From code/mini-input/host.py:

# from code/mini-input/host.py
if mode == "url":
    report = inspect_url(params["url"])
    if not report["ok"]:
        self.refused.append(("url", report["block"]))
        return {"action": "decline"}
    r = self.person.ask(self.server_name, params["message"], None, url=params["url"])
    if r["action"] == "accept":
        self.opened_urls.append(params["url"])          # opened by the user's browser, not by the model, and never fetched by the host

Read it as: the comment on the last line is the entire security property of URL mode in one clause. The host records that the URL was opened. But it is explicit that the opening happens in the user's own browser. The host never fetches it or shows it to the model. That is the one guarantee form mode cannot give a secret.

Form mode, URL mode

Form mode asks for structured data through a flat schema the client can render and validate. URL mode sends the person to a page outside the client, for anything that must not pass through the client: sign-in, payment, or a secret.

Example: a form titled "Paste your cloud API key" is refused before it ever reaches the person, while the identical request renamed to "Paste the value we emailed you" gets through. That is the honest limit of a form-mode screen: a rule for the server author to follow, with the host's check only as a seat belt, not a substitute.