How to use GPT-5.4 mini with a signed-in browser

GPT-5.4 mini can call tools, but that alone does not give it access to a signed-in website. Use an agent client that can run local tools, expose Tabbit CLI to that client, and verify the CLI reaches the Tabbit profile where you signed in. OpenAI still lists the model in its API documentation. Since August 31, 2026, Codex no longer offers it to ChatGPT-authenticated users, while API access and Codex sessions using an API key remain available.

Check four layers separately: the provider serves the model, the client can select it, the client can invoke a local browser tool, and the selected Tabbit profile is signed in to the site. A failure at any layer can look like “the model cannot browse.”

Check the model route first

OpenAI’s model page lists gpt-5.4-mini and the dated snapshot gpt-5.4-mini-2026-03-17. It supports function calling, and the Responses API lists computer use among its tools. That describes OpenAI’s API, not every client. A client with its own model catalog may use another ID or omit the model. Read OpenAI’s model reference and Codex access notice before changing browser settings.

If the model is missing, check the client’s authentication method first. Updating Tabbit will not restore a model that the client account cannot select. See the GPT-5.4 guide and Codex browser-control guide.

Verify the local browser connection separately

Install Tabbit Browser and load the Tabbit skill in your agent client. Skill discovery varies by client: some read a configured skills directory, while others offer a named command such as Pi’s /skill:tabbit. Do not assume every agent recognizes /tabbit or that model tool support installs a skill. Restart the client if needed. Confirm it can read the skill instructions and run the local launcher. Start with the Tabbit CLI quick start; the CLI tutorial explains tasks and receipts.

Run diagnose first. If several Tabbit instances are open, select the intended instance ID shown by the launcher and keep that choice for the task. Then create a named task and read a harmless page before opening a signed-in site:

launcher="$HOME/.local/bin/tabbit-cli"
"$launcher" diagnose
export TABBIT_PLAYWRIGHT_INSTANCE="<observed-16-hex-instance-id>"
"$launcher" nodejs --task "GPT mini release-note review" --request-id gpt-mini-open-01 <<'JS'
await page.goto('https://example.com/', { waitUntil: 'domcontentloaded' });
return { title: await page.title(), url: page.url() };
JS

Local runtime, permission to launch a process, model availability and website login are different prerequisites. A cloud agent might load the skill but still be unable to reach your computer’s browser. Compare Browser MCP vs CLI and see how to connect an agent to an existing browser.

Sign in yourself, then verify the page

Open the target site in the exact Tabbit profile selected for the task and sign in yourself. Ask the agent to read a non-sensitive heading or status first. A named task organizes pages and request history; it does not create an account or guarantee that every profile shares cookies. A local fixture recorded for the Tabbit CLI guide returned 401 before sign-in and let a second named task read the same fixture after sign-in in the selected browser environment. That verifies the fixture only, not session persistence on every site or access from a remote agent.

A Reddit user who described repeated login forms, 2FA and bot checks wrote: “the agent shouldn't be good at proving it's a human. it should inherit a session where that was already proven.” The same thread mentions session expiry and cookie handling. This is one person’s experience, not a recommendation to export cookies. Keep passwords and session tokens out of prompts.

Create a named draft and stop for review

For a release-note review, ask the agent to read the page’s visible title and status, then prepare a document named GPT-5.4 mini release-note review. Allow a draft save only. Require it to report the visible draft status and stop before publishing, sending or changing account settings. Keep the draft in a separate task so you can continue other work. Review the source and text yourself before any external action.

This prompt is an illustrative workflow, not a test against a production release-note system:

Use the selected local Tabbit task named "GPT mini release-note review".
Open the release-notes URL I provide. Read only its visible heading, date and status.
Create a document draft named "GPT-5.4 mini release-note review" with the source URL, visible title, date, status and a short summary supported by that page.
Do not publish, send, delete, change settings or submit a form.
If login is required, stop and ask me to sign in. If the page is ambiguous, quote its visible wording and mark it unclear.
After saving, report the draft title, URL and visible Draft status. Stop for my review.

A commenter in r/mcp recommends a separate browser profile with only the accounts needed for a task, plus human approval before anything submits, pays or sends. That is a design choice, not a guarantee against prompt injection. Keep the site list narrow and verify what the agent can actually do. Leave the final irreversible action to a person.

For permission details, read Claude Code browser permissions, how to check an agent’s research citations, OpenClaw browser setup and the agent-browser CLI tutorial. If an agent sees but cannot click a control, see button troubleshooting. The Codex setup guide covers one client route.

The practical answer

GPT-5.4 mini can handle a signed-in browser task when the model provider, local agent client, Tabbit CLI and selected browser profile all work together. Start with a read-only check, sign in yourself, name the task and ask for verifiable output. Keep edits in a named draft and stop at a visible review checkpoint. If the model is missing from Codex with ChatGPT sign-in, check the announced retirement before changing browser settings.

Sources

• OpenAI GPT-5.4 mini model page, API ID and tool support; checked 2026-11-10.

• OpenAI ChatGPT/Codex changelog, retirement and API-key exception; checked 2026-11-10.

• Tabbit CLI quick start, official setup reference; checked 2026-11-10.

• Tabbit CLI tutorial, task and receipt workflow.

Secholar.L

Growth & Content at Tabbit

Secholar.L writes hands-on guides about AI browsers and agent workflows, comparing tools with real research and citing verifiable sources.