To compare a signed-in dashboard with yesterday’s snapshot using GPT-6.1 Sol, install Tabbit Browser and run Tabbit CLI from a compatible local agent. Check that your account can select gpt-6.1-sol. Then let the agent collect the visible changes in a separate task tab and leave the comparison in a browser draft you can review. OpenAI release
A Codex user described keeping a ChatGPT subscription mainly for computer use and called Codex strong at browser work. That is one user’s preference, not a benchmark. This guide turns the dashboard task into a read-only recipe: report what changed, link each page, and leave the final interpretation to a reviewer.
Key takeaways
The model is only one part of browser use. The runtime, agent client, local browser tool, and site login each need a separate check.
Use Tabbit Browser for the signed-in workspace, and Tabbit CLI from a local agent for controlled page reads.
Keep the first run read-only. Name its output and ask a person to review it in the browser before saving or sharing.
A remote agent needs a separately supported local handoff; it cannot inherit a desktop session by assumption.
Check the selected Sol model ID and execution environment
| Check | What to verify | Stop if |
|---|---|---|
| Model availability | Selected client actually lists the model, or your local runner loads the checkpoint | Model is absent or runner fails to load |
| Tool execution | Client can run the Tabbit Skill or installed CLI locally | Only cloud tools are available |
| Browser ownership | Tabbit Browser is on the same device as the local agent | Agent runs remotely without a supported handoff |
| Site session | The intended Tabbit profile is already signed in | Page asks for login or displays the wrong account |
Skill discovery is separate from launcher reachability. A client might recognize /tabbit but still lack shell permission; a working tabbit-cli binary does not prove the model is selectable. Check both. Some clients use /skills; Pi uses /skill:tabbit. Use the syntax shown by your client.
According to the official model documentation, OpenAI lists GPT-6.1 Sol in ChatGPT Work and Codex for eligible plans and exposes gpt-6.1-sol through its API. These are OpenAI product/API paths, not proof that an unrelated agent client supports the model. Tool calling needs an application or local client to provide the browser tool. No public weights are available in the sources checked.
Make a dashboard change log, not a verdict
A useful first task reads a dashboard, compares its visible values with a supplied snapshot, and returns only changed rows. Ask for the old value, new value, timestamp, and exact page URL. Treat the model’s explanation of why a number changed as a hypothesis unless the page states the reason.
| Output field | Why include it | Reviewer question |
|---|---|---|
| Page URL | Lets the reviewer open the same source | Does this link point to the right workspace? |
| Previous and current value | Makes the change concrete | Are both values visible and comparable? |
| Updated date | Sets the comparison window | Is the date current and in the right timezone? |
| Uncertainty note | Prevents a guess from becoming fact | What evidence is missing? |
OpenAI’s product and API routes are not interchangeable. A ChatGPT Work or Codex entitlement does not automatically provide API credentials, and API access does not automatically attach a local browser. The agent client must actually offer Sol and provide a local browser tool. If that pairing is unavailable, let Sol analyze a copied, non-sensitive export and hand the page-checking list to a local agent or person.
A Codex thread says the author kept a subscription mainly for computer use. Another user in the same thread recommended a faster model for some work. Preferences differ; your dashboard’s data sensitivity and review cost matter more than a short thread. Keep any write action outside the first run.
Use the prior snapshot as the comparison baseline
This asks for a named draft, source links, explicit uncertainty, and a stop before any write action.
Read the signed-in dashboard pages I list. Compare the current status and visible updated date with the previous snapshot I provide. Return only changed rows with page URL, old value, new value, and confidence. Put ambiguous items under “Needs review”. Save the output as “Sol dashboard changes — draft”. Do not change dashboard data, send messages, or click publish.A practical browser option: Tabbit Browser
Tabbit Browser is useful when the task depends on a website where you are already signed in. Install it, sign into the target site in the profile you intend to use, and let the local agent call Tabbit CLI for a bounded read. The CLI works in a separate task space, so you can keep using your other tabs while it gathers the requested fields. Review the draft in the browser before any write action.
This is a workflow recommendation, not a claim that the model ships with Tabbit integration. The model provider, the agent client, and the browser bridge are separate components. Verify the model selector and local tool permission in the client you choose. Tabbit cannot make a cloud-only runner local.
For setup details, see the CLI guide, existing-browser connection guide, first task checklist, MCP versus CLI guide, Codex setup, agentic browser explainer, browser agent guide, and Tabbit Browser overview.
“I don’t know what it is but Codex is phenomenal at browser use.”
u/lumoflow on Reddit. This is an individual report, not evidence of a general capability or availability.
“You can always tell it to handle a certain configuration/form/etc but not submit since you prefer her to handle the final step after review.”
u/cankle_sores on Reddit. This is an individual report, not evidence of a general capability or availability.
Sources and community notes
According to the official model documentation, OpenAI lists GPT-6.1 Sol in ChatGPT Work and Codex for eligible plans and exposes gpt-6.1-sol through its API. These are OpenAI product/API paths, not proof that an unrelated agent client supports the model. Tool calling needs an application or local client to provide the browser tool. No public weights are available in the sources checked.
Sources
FAQ
Does selecting the model give it browser access?
No. The client must connect browser tools to the intended profile. Verify access with a harmless read.
Can it reuse my existing website login?
Yes, when local Tabbit CLI connects to the Tabbit Browser environment where you signed in. Never share credentials with the model.
Is `/tabbit` available in every client?
No. Skill discovery varies. Some clients use `/skills`; Pi uses `/skill:tabbit`. Check the client’s actual syntax.
Can a cloud runner reach my desktop browser?
Only through a separately supported local handoff. Do not assume a cloud runner can reach your device.
Should I let the agent publish its draft?
Keep the first task read-only. Review the named draft in Tabbit Browser before any write.
What if my client cannot select this model?
Check the client’s model list, provider settings, and runner support. Public availability does not prove client compatibility.