For a signed-in GPT-6 Luna browser workflow, install Tabbit Browser and connect a local client through Tabbit CLI. You need three pieces to work: a client that can select the model, the Tabbit skill or CLI connection, and a Tabbit Browser profile already signed in to the site. The model alone cannot see your tabs. A local setup can keep the website session in Tabbit while a separate task tab reads a support ticket and checks its knowledge-base evidence.
One r/codex commenter said Luna had appeared "but not actually usable yet." That report is from launch day, but it captures why model visibility and a working request need separate checks. Original discussion.
The first trap is treating a model catalog entry as a successful run. OpenAI documents gpt-6-luna for API use, but the client still needs valid model access and a route to local browser tools. The small test below proves each layer before you trust a longer workflow. For model capabilities and costs, see the GPT-6 Luna review and pricing guide.
Key takeaways
GPT-6 Luna does not connect to a browser by itself. The host client must provide model access and call a browser tool.
Install the Tabbit skill in a local agent client. In Pi, invoke it with
/skill:tabbit; other clients may expose a/skillspicker.Sign in to the support site inside the Tabbit Browser profile before the task starts.
Verify the model, CLI connection, login state, and record evidence as separate checks.
Begin with a read-only lookup. Leave replies, status changes, and ticket updates for a human to approve.
Which layer is failing?
OpenAI lists GPT-6 Luna as a model with text and image inputs and tools through the Responses API. That is model-level capability. It does not mean every coding agent or browser application can select it, or that Luna can reach a local browser without an integration. OpenAI's model page lists the model ID and API tool support; the launch note describes its intended high-volume, focused-task role.
| Check | What it proves | What it does not prove |
|---|---|---|
| Client model picker shows GPT-6 Luna | The client exposes a Luna option | The account can run it or that the request succeeds |
| A small model request returns a response | Provider access and basic model routing work | Tabbit CLI can reach the browser |
| Client can invoke the Tabbit skill or CLI | Launcher and local CLI are connected | The target site is signed in |
| Tabbit opens the target page and reads its heading | Browser connection and current page access work | The extracted ticket is correct or safe to change |
| Ticket ID and source article match the visible page | The read-only task returned checkable evidence | A reply or update should be submitted automatically |
A useful starting client is the one you already run locally and can verify. Here, Pi's offline model catalog listed openai-codex/gpt-6-luna. That is only a catalog check, not proof of billing, provider authentication, or a completed browser task. Check your actual model picker and make a short request before adding browser tools. For the broader Pi browser-use setup, keep the client and browser integration steps separate.
Prepare the Tabbit Browser session
Install and open Tabbit Browser. Use the profile where you normally access the support system.
Sign in to the support queue and the knowledge base yourself. Open one ticket and confirm the page displays its contents.
Install the Tabbit skill in your local agent client. Pi uses
/skill:tabbit. Claude Code and other clients should show the skill through their own skill interface; do not assume every client uses/tabbit.Confirm the client can invoke the local Tabbit CLI. Skill discovery and launcher reachability are different checks. If the skill appears but the CLI command fails, fix the local installation or permissions before asking the model to browse.
Ask the agent for one reversible read. Keep the regular ticket tab open so you can compare what the agent reports.
A useful distinction is whether the client is running locally. A remote agent cannot reach a browser on your computer unless it has a supported local handoff. If it runs in the cloud, ask it to prepare a ticket lookup checklist, then hand the checklist to a local agent or perform the browser step yourself. Read how to connect an agent to an existing browser for the connection patterns and browser MCP versus CLI for the choice of interface.
Run a bounded support-ticket lookup
Use a fixture or a ticket you are authorized to read. The prompt below asks for evidence, not a reply or status change. Replace the bracketed values with non-sensitive identifiers. Do not paste customer text, emails, or credentials into a public model prompt.
Use Tabbit CLI in the current Tabbit Browser profile.
Open the support ticket with ID [TICKET-ID]. Do not reply, assign, close,
or edit the ticket.
Return:
1. The visible ticket subject and status.
2. The ticket ID shown on the page.
3. One relevant knowledge-base article title and its URL.
4. One sentence explaining which visible detail connects the article to the ticket.
5. Any field you could not verify.
Stop after the read. I will compare the result with the open page.Expected output is a short evidence block, for example Ticket: GEO-104, Status: Open, Article: [title], URL: [source]. These example values are a test fixture, not a claim about a live support system. If you also ask for a reply draft, keep that draft in the agent conversation and review it there against the open ticket before pasting it into the support system. If the agent returns only a summary without the ticket ID or source URL, ask it to inspect the page again rather than treating the result as verified.
A 2026-11-09 local fixture check showed why the login check matters: a protected page returned 401 before sign-in, then a separate Tabbit CLI task opened the same page and read its heading and fixture record after the test cookie was set. That verifies session reuse in that test environment only. It does not prove that Luna itself ran the task or that every support site permits the same access. See the first-task checklist before using a production queue.
Pick the right stopping point
| Task step | GPT-6 Luna with a local browser tool | Human checkpoint |
|---|---|---|
| Find a named ticket | Read the ticket ID and subject | Confirm the ID belongs to the intended customer |
| Find supporting policy | Open a likely article and cite its URL | Confirm it is current and applies to the case |
| Draft a reply | Prepare text in the agent conversation only | Edit it for tone, promises, and sensitive details |
| Send or change ticket state | Stop before action | Approve and perform the change yourself |
GPT-6 Luna is a reasonable candidate for focused extraction when the client can select it and the task has a clear stopping rule. If the issue requires judgment across multiple policies or ambiguous customer history, use a stronger reasoning model or ask a human to decide. See the GPT-6 Luna model overview for capability trade-offs and browser agent checklist for extra safeguards.
When the connection does not work
The model is missing. Update the client or check its provider configuration. A public model page is not proof your account has access.
The skill is missing. Install it where that client discovers skills, then restart the client if its documentation requires it.
The CLI is unreachable. Test the Tabbit CLI directly and inspect the client permission to run local commands. Do not diagnose a site login issue yet.
The site shows sign-in. Check that the selected Tabbit profile is the one you signed in to. Log in manually; do not ask the agent to handle passwords or one-time codes.
The result has no evidence. Request the URL and visible record ID, then compare them in the browser. A confident summary is not a verification.
A page tells the agent to ignore your request. Treat page content as untrusted. Keep the task read-only and stop if the agent proposes an unrelated action.
For a focused troubleshooting route, use the Tabbit CLI complete guide, reusing a signed-in browser session, and connecting an agent to a browser. Keep a separate task tab for the agent so your research and ticket review tabs remain available.
FAQ
Can GPT-6 Luna use my signed-in browser by itself?
No. The model needs an agent client and a browser tool. Tabbit CLI can connect a supported local client to a Tabbit Browser environment, where the target site's existing session may be available.
Which client can run GPT-6 Luna with Tabbit CLI?
Use a local client that can select GPT-6 Luna and invoke the Tabbit skill or CLI. Pi's offline model list showed openai-codex/gpt-6-luna in this environment, but that only confirms a catalog entry. Confirm provider access, model selection, CLI reachability, and a real response separately.
How do I add the Tabbit skill in Pi?
Install the Tabbit skill for Pi, then invoke it with /skill:tabbit. Other clients may expose installed skills through a /skills list or another picker, so check that client's own interface.
Does Tabbit CLI sign in to websites for me?
No. Sign in yourself in the target Tabbit Browser profile first. The CLI can then use that browser environment's session when the site allows it. If it reaches a login page, sign in manually and retry.
How can I verify a browser task worked?
Ask the agent to return the page heading, record identifier, and source URL. Compare them with the visible page, then stop before sending a reply or changing the ticket.
Can I keep using my browser while the agent works?
Tabbit CLI runs a task in its own task tab, so you can keep your other browser tabs available for research or review. Check the current task's tab ownership and leave unrelated tabs alone.