Claude Sonnet 5.5 can help transfer selected facts from a signed-in page into a form draft when a local agent client can run Tabbit CLI. Keep the target form open in Tabbit Browser, give the agent a source-to-field mapping, and stop before submission. A Reddit user reported that Sonnet 5.5 could not read several support sites during a troubleshooting task. That is one person’s experience, and the thread also points to site blocking and page rendering as possible causes, not just model choice. The handoff below keeps the source page visible in the user's signed-in browser, but a site can still block access. Anthropic's Sonnet 5.5 release page documents the model and API route; it does not establish a Tabbit integration. The general Sonnet 5.5 guide covers model use, while this recipe focuses on a controlled browser handoff.
Key takeaways
A model route does not provide browser access or a website login.
Use a local client that can discover the Tabbit skill and execute Tabbit CLI.
Copy only fields you are authorized to read and enter.
Keep the destination form in draft and stop before submit, save, or send.
Review each value against the source page before you act.
Check the four layers before copying
| Layer | What to confirm | If it fails |
|---|---|---|
| Sonnet model | claude-sonnet-5-5 appears in your provider/client | Check account access and provider setup |
| Agent client | It can load local skills and run permitted shell tools | Use another supported local client or hand off steps |
| Tabbit CLI | It reaches the intended Tabbit Browser environment | Diagnose local launcher and instance routing |
| Website session | The source and destination pages open while signed in | Sign in yourself in that browser, then retry |
Anthropic lists Claude Platform, AWS, Google Cloud, and Microsoft Foundry as Sonnet 5.5 routes. A chosen agent client may expose only some providers. Confirm the model name in that client's current picker and documentation. Do not infer a model route from the browser connector.
Prepare a source-to-field map
Use a harmless test form first. Write down the exact destination field and the source label the agent should read. Never include passwords, tokens, personal identifiers, or private values in the prompt unless the task and tool are explicitly authorized to handle them.
| Destination field | Source evidence | Copy rule | Human check |
|---|---|---|---|
| Subject | Visible page heading | Copy exact wording | Compare spelling and context |
| Reference ID | Label next to record | Preserve punctuation | Confirm it belongs to the right record |
| Summary | Named source paragraph | Short factual paraphrase with source URL | Check no inference became a fact |
| Due date | Explicit date label | Preserve displayed date format | Confirm timezone and year if shown |
Run a draft-only transfer
In OpenCode, the documented skill call is @tabbit when the skill is discovered through its configured skill directory. Other clients use their own /skills or skill discovery interface. The launcher must still reach Tabbit locally, and the site login must already exist in that browser profile. These are independent checks.
Use the local Tabbit skill and Tabbit CLI from this agent session.
The source page and destination test form are already open in my signed-in Tabbit Browser.
Read only these source labels: [label A], [label B], [label C].
Map them to these destination fields: [field A], [field B], [field C].
Do not click Save, Submit, Send, or any control that changes data.
Return a table with destination field, exact source label, proposed value, source page title and URL, and uncertainty.
Enter the values only if the form supports an unsaved draft and the client can verify each field. Otherwise return the mapping without typing.
Name the draft "Sonnet source transfer 01". Stop before submission and show me every value for review.This prompt is an illustrative workflow. The user must confirm that the site permits draft entry and inspect the rendered fields. If the destination has autosave, the agent should not type; a “draft-only” instruction cannot override the site's behavior.
Review the draft before any submission
Use a second pass to check source and destination side by side. A filled input is not proof that the right record was selected. Verify the record identifier, date, spelling, and any summarized text against the visible source.
| Review item | Evidence to compare | Stop condition |
|---|---|---|
| Record identity | ID and page title | Source record is ambiguous |
| Copied value | Exact source label and displayed text | Value is missing or transformed unexpectedly |
| Destination | Field label and current form | Form changed or autosaves unexpectedly |
| Final action | Submit/save/send control | Do not activate until you approve the complete draft |
Tabbit Browser lets you keep working in other tabs while a task tab holds the source and draft. Tabbit CLI connects the local agent to those task tabs; it does not provide Anthropic API access or make a cloud runner local. For setup and boundaries, see Tabbit CLI setup, connecting an agent to an existing browser, the first browser-agent task checklist, CLI or browser MCP, Codex setup, browser tools for agents, browser security risks, install Tabbit Browser.
When to use this handoff
Use it for a small, reversible form draft where every field has a visible source. Keep human review for any regulated, financial, account, or consequential submission. If the model cannot cite the exact page and label, leave that field blank. If your client cannot execute a local skill, ask Sonnet to produce the mapping table and hand it to a person or local agent that can reach Tabbit Browser.
A good first run uses a test record, one or two fields, and no submission. Inspect the named draft, then decide whether to repeat with the real task.
FAQ
Can Claude Sonnet 5.5 use a signed-in browser by itself?
No. A local agent client must run a browser connector such as Tabbit CLI, and the target site must already be signed in inside the Tabbit Browser environment the connector reaches.
Can Sonnet 5.5 submit the form?
This workflow stops before submission. Review every copied field and use the site yourself to submit only after you approve it.
What should I verify in the API route?
Anthropic identifies the API model as `claude-sonnet-5-5`. Confirm the provider, account access, and model availability in your chosen client before setting up browser tools.
Will the browser reuse my website session?
It can reuse the session already present in the specific Tabbit Browser environment reached by the local CLI. Skill discovery, CLI reachability, and site login are separate checks.
What if my agent is cloud-hosted?
A remote runner cannot see your local browser unless the client supports a local handoff. Ask it to produce a field-mapping plan, then pass that plan to a local agent or carry it out yourself.
Is this the same as the Claude in Tabbit guide?
No. The existing guide covers general model use in Tabbit. This page is a specific local-agent recipe for copying approved source fields into a form and stopping before submission.