Install Tabbit Browser and run Tabbit CLI from a compatible local agent. Claude Haiku 5.5 can be used in an authenticated browser workflow only when the selected host and local agent expose the model and browser tools. For a ticket check, have a local agent call Tabbit CLI, read the visible ticket number and link, and stop with an evidence checklist. Tabbit can reuse the login in its selected browser environment; the model API, agent skill, CLI route, and website session each need their own check.
Verify the route before opening a ticket
Anthropic's current platform documentation lists Claude Haiku 5.5 and a browser-use tool for API workflows. That does not mean Claude Code, Claude's consumer app, or every third-party client exposes the same tool or model route. Confirm claude-haiku-5-5 in the selected provider/client and confirm it can run local tools. Install the Tabbit skill using that client's documented setup. Use /tabbit only when named skills are supported, /skill:tabbit in Pi, or the client's /skills discovery command where applicable.
In Tabbit Browser, open the intended support queue and verify the account. Give the agent one ticket and ask it to return the visible ticket ID, title, status, and canonical link with page evidence. Store its report as ticket-check-104, then compare each item with the page. It should not reply to the customer, change status, or create a note. Its task tab stays separate so you can keep working in the browser.
| Gate | Confirm | Stop if |
|---|---|---|
| Model | Provider exposes claude-haiku-5-5 | Model alias differs or is unavailable |
| Tool route | Local agent can invoke Tabbit CLI | Agent is remote without local handoff |
| Ticket | ID and status visible on the correct account | Access denied or multiple matches |
| Requested field | Evidence | Review |
|---|---|---|
| Ticket ID | Exact visible ID | Match the page URL and heading |
| Status | Exact visible label | Check for stale or pending state |
| Link | Current ticket URL | Confirm it resolves in the right account |
For setup details, read the Tabbit CLI tutorial, existing-browser guide, browser-agent checklist, MCP vs CLI comparison, Codex setup, Claude Code setup, the published Haiku-in-Tabbit guide, and the Sonnet 5.5 guide.
Anthropic's browser-use tool is a model-host API capability with a specific tool contract. Tabbit CLI is a local browser route that a compatible agent can call. They are not the same integration. Do not assume Haiku's API browser tool automatically sees Tabbit's logged-in profile; the local agent must explicitly bridge to Tabbit CLI, and the selected host must allow the model call.
In a small Claude Code experiment, one tester repeated identical Haiku 5.5 tasks and saw different results across runs. Repeat the same read-only ticket check and compare the ID, status, and source with the page each time. Original test
Review before changing the ticket
Use Claude Haiku 5.5 only if this provider and local agent confirm the model is available.
In the currently open Tabbit Browser page, inspect support ticket 104 only.
Return the exact visible ticket ID, title, status label, and current page URL.
For each value, quote the visible text that supports it. If there is no exact match, return no-match. If access is blocked, return needs-human-check.
Save your report as the draft ticket-check-104. Do not reply, change status, add a note, or submit anything. Show me the report and wait.This prompt is an editorial example, not a tested Haiku or client integration.
Use a named draft and a visible checkpoint. Ask the agent to show the ticket ID, status text, and link, then open the link yourself before taking action. If the queue loads the wrong account, stop and select the correct Tabbit profile yourself. Keep credentials and one-time codes out of prompts. Remote runners need a separately supported local handoff to reach Tabbit on your machine.
Tabbit Browser fits when the workflow depends on a website session you already have open and you want the agent task to run in a separate tab context. Project research tested login reuse on a local fixture across two CLI tasks. It did not test Haiku 5.5, the Anthropic API browser tool, or a production ticket system.
FAQ
Does Haiku 5.5 include browser access by default?
No. Anthropic documents a browser-use API tool, but your host and agent client must expose it and be configured for it.
Can I call Tabbit CLI with Haiku?
Only through a compatible local agent that can run the selected model and invoke Tabbit CLI. Check both routes first.
Will it use my logged-in support account?
The local agent can use the selected Tabbit browser environment. Confirm the correct profile and account in the browser.
Can Haiku reply to tickets in this workflow?
No. The example only reads a ticket and saves a report for review.
Is Claude Haiku 5.5 in the existing Tabbit model picker?
The published Haiku article says availability depends on the live account picker. Check your own account; this CLI workflow does not imply picker access.
Has the sample prompt been run with Haiku 5.5?
It is a proposed workflow. First check it in a test queue that you can access.