To compare how GPT-6 Sol reads a signed-in test page, install Tabbit Browser and call Tabbit CLI from a compatible local agent. Select gpt-6-sol, keep the page and requested fields fixed, and save the observed values in a draft for comparison. OpenAI model documentation
One r/codex user reported instruction-following problems with GPT-6 Sol on an HTML task. That is one person’s account, not a controlled test, but it is a reason to verify a small browser task before trusting a longer run. Original discussion.
Key takeaways
GPT-6 Sol is the model, not the browser connection.
Check model access, client skill discovery, and local CLI reachability separately.
Sign in yourself in the intended Tabbit Browser profile.
Keep the first task read-only and require evidence.
What the official model page confirms
The official model page documents the provider’s model identifier and listed capabilities. It does not certify that your account, agent client, or browser connection can use the model. For GPT-6 Sol model background, see the GPT-6 Sol overview and pricing page. Do not confuse model support for tool calling with a working local browser route. GPT-6 Sol is separate from GPT-6.1 Sol.
| Check | Proves | Does not prove |
|---|---|---|
| Model appears in picker | Client knows a model label | Account access or successful request |
| Short model request succeeds | Provider credentials and routing work | Tabbit CLI is connected |
| Tabbit skill runs | Client can reach local launcher | Site is signed in |
| Page values include IDs and URLs | Claims can be checked | Permission to make changes |
Prepare Tabbit Browser
Install Tabbit Browser and sign in to the target site yourself. Install the Tabbit skill where your local client discovers skills. Pi uses /skill:tabbit; some clients use /skills. Finding the skill and launching the CLI are separate checks. Use a separate task tab to keep your ordinary research tabs available. A cloud agent needs a separately supported local handoff; otherwise ask it to prepare steps for a local client. See the Tabbit CLI guide, browser connection guide, login reuse guide, and first-task checklist.
Compare GPT-6 Sol on a fixed test page
The task compares what each model reads from the same harmless test page. Keep the page, prompt, browser profile, and output fields identical. Keep the example separate from any customer or production data. The project’s local Tabbit fixture showed that a second task tab could read a signed-in test page after login. That verifies session reuse in the fixture only; it was not a model-specific run.
Use Tabbit CLI in the current Tabbit Browser profile. Open [TEST URL] and read record [FIXTURE-ID]. Do not click buttons, change values, or submit. Return the page heading, exact record ID, requested fields, source URL, and anything you could not verify. Show the named draft “Sol page read test” in the browser. Stop for review. I will repeat it with the same page and fields using another model.Expected output is a concise evidence table: visible label, value, record ID where applicable, and source URL. Example values are placeholders, not a recorded model run. If a field cannot be checked on the page, leave it unresolved.
| Stage | Pass evidence | Stop and inspect when |
|---|---|---|
| Model | The intended provider returns a response | Model ID is missing or access is denied |
| Client | Tabbit CLI opens a task tab | Skill appears but launcher fails |
| Page | Expected account and content are visible | Login page or unexpected account appears |
| Result | Each field maps to a visible source | IDs, dates, or units disagree |
Keep a human checkpoint
| Action | Agent role | Human review |
|---|---|---|
| Read page | Extract named visible fields | Confirm the account and page |
| Explain | Draft a short summary | Check definitions and context |
| Fill test form | Enter reviewed values only | Compare each field with source |
| Submit or edit live data | Stop before action | Approve and perform the change |
GPT-6 Sol and GPT-6.1 Sol are different models. Compare GPT-6 Sol only under fixed conditions and treat one task as a practical check, not a benchmark. For the choice between a browser integration and a remote tool, read browser MCP versus CLI. The related Codex setup guide, browser safety guide, local browser-agent guide, and AI browser workflow guide provide additional context.
FAQ
Can the model open a signed-in browser by itself?
No. A local agent client and browser integration are required.
How do I invoke the Tabbit skill?
Pi uses `/skill:tabbit`. Other clients may show a `/skills` picker or their own documented entry point.
Will Tabbit CLI sign in for me?
No. Sign in yourself in the selected Tabbit Browser profile first.
Can I use a remote agent?
Only if it has a supported local handoff. Otherwise pass its checklist to a local client.
What should the first task do?
Read a small, authorized page and return source URLs and visible identifiers.
Should the agent submit changes?
Keep the first run read-only. Review any proposed changes before applying them.