Models

The support agent

Answers a customer from one product's own record, and is scanned on the way out for the things it must never say.

A product surface, not a published identifier. It runs on the shared inference path and carries no identifier of its own.

What it is for

The support agent answers questions from an operator's customers about that operator's product. Its whole context is the product record: the specifications, the offer row with its observed figures and their bases, and the store manifest.

It is the only FlowFinds surface whose output reaches someone who is not the account holder, which is why two of its rules are enforced on the text rather than asked for in its instructions.

What it can do

Record-bound answering

A question the record answers is answered from the record. A question it does not is refused by name — we do not have that on record, so we will not guess — and handed to a person.

Output scanning, not output trust

It never states a shipping cost, customs charge, duty, import fee or delivery caveat, and the outgoing text is scanned for them. A rule that lives only in an author's intention is not a control.

The tense rule carries through

An observed undercut may be stated flatly because it was observed. The margin is declared by the owner and is never quoted to a customer at all. A price carries the date it was checked, and any failed refresh, through the same resolver the offer screen and the storefront use, so the three cannot disagree.

The inference path

PropertyValue
RuntimeCodex CLI, one ephemeral session per request
Modelgpt-5.5
Reasoning effortmedium
Sandboxread-only by default; workspace-write only where an edit is being applied
IsolationThe caller supplies an already-authorised account workspace as the working directory. No session state is shared between founders, and workspace-write never extends above that directory.
Pinned flagsexec --ephemeral --ignore-user-config --skip-git-repo-check --output-last-message

The session is ephemeral and ignores any user configuration on the host, so a response cannot be shaped by state left behind on the machine. A refusal from the runtime is read out of its own event stream and passed through in its own words: an account out of credits reports that, rather than a generic failure the operator can do nothing about.

How it is measured

Not covered by commerce-v1.

Because no recorded run exercises this surface, this page states no measurement of it at all. The benchmark and its system cards are published under research; they describe commerce-reasoning-v1 and nothing else.

Its limits

Where these facts come from

Each line names a file in the implementation. The descriptions on this page are a transcription of those files and are marked provisional at their source until they have been checked against it again.

The others

Back to all models, or read what the engine is used for under the product.