Inkling 2 Small can work with a signed-in browser through a local agent that runs Tabbit CLI, but the model itself does not control a browser. As of November 9, 2026, OpenCode lists an Inkling 2 Small Free route. OpenCode warns that free-period prompts may be retained and used for model monitoring or training, so keep confidential tickets out of that route. OpenCode model list · Thinking Machines release
One r/singularity commenter pointed out that “the weights aren't out yet.” This is an access concern, not a model test. Original discussion
Key takeaways
The model, agent client, Tabbit CLI, browser profile, and website login are separate pieces.
OpenCode's provider ID is
inkling-2-small-free; the canonical catalog ID isthinkingmachines/inkling-2-small.OpenCode's skill ID syntax is
@tabbit. Its shell tool runs on the host, where the installed CLI must be reachable.A Tabbit task may reuse the selected profile's site session. Check account and workspace first.
Stop at a named draft. Reading a page is not approval to edit or send a ticket.
Pick the model route
| Route | Verified detail | Risk or limit | Use it when |
|---|---|---|---|
| OpenCode Inkling 2 Small Free | Model and endpoint appear in OpenCode's listing; catalog reports tool support. | Free-period data may be retained for monitoring or training. | The data is non-sensitive or approved for this provider. |
| Thinking Machines Tinker | Publisher says Inkling 2 Small is available for inference and fine-tuning. | No Tinker-to-Tabbit client pairing was tested. | Your local agent can call Tinker and run shell tools. |
| Other API | No other route was verified here. | IDs and tool-call behavior vary. | Only after checking the provider's current model list. |
The two IDs are not interchangeable. Models.dev lists the provider mapping; the OpenCode model docs list its route.
Connect OpenCode to Tabbit locally
Install Tabbit Browser and follow the Tabbit CLI quick start. Check that OpenCode discovers the tabbit skill, then mention @tabbit or load it with the skill tool. The OpenCode skills guide documents discovery; its shell tool runs commands on the host.
Run the installed launcher's diagnose. Confirm the intended Tabbit instance, then sign into the ticket site in that profile yourself. Skill discovery, launcher access, and site login are separate checks. Cloud model inference may still receive page text. Read connecting an agent to an existing browser and the first-task checklist before using a work account.
Read a small ticket queue
Start read-only. Ask the agent for a source-linked table and a visible draft, not a reply to the customer.
Review the first five tickets in the currently open support queue.
Use the Tabbit skill and read only the visible list and public status panel.
Do not open attachments or hidden fields. Do not assign, edit, save, or send.
Return ticket ID, exact visible status, assignee, and page URL.
Write "not visible" for missing fields. Do not infer.
Prepare a browser draft named "Inkling queue review — 2026-11-09" with the table and uncertain rows.
Stop before saving or sending. Show the draft for review.Expected output is at most five rows with exact IDs and links. Verify each row in Tabbit. If the account, workspace, or queue differs, stop and ask the account owner to choose the right target.
Use a visible checkpoint
| Check | Verify | Continue only if |
|---|---|---|
| Skill | OpenCode loaded tabbit. | The task uses the actual CLI workflow. |
| Launcher | tabbit-cli diagnose shows the intended instance. | It is the profile you signed into. |
| Page | Ticket ID, title, status, and URL. | Account and workspace match. |
| Draft | Named draft against every source row. | You approve each specific write. |
For connection choices, see Tabbit CLI versus browser MCP. Login state and task organization differ; see profiles, workspaces, and tab groups. The complete CLI guide and Codex setup cover broader setup. How agents control browsers gives the general handoff model.
When Inkling is a poor fit
Do not send confidential support records through the free hosted route unless your organization approved its retention terms. Thinking Machines says full weights are planned after safety testing; that plan does not mean you can run them locally today. Its release post also notes limitations in concise communication and tool choice. Keep the job small and verify every field.
Verdict: Inkling 2 Small may provide the model response, but the local agent and Tabbit CLI provide the browser path. Use an approved provider, a read-only task, and a visible draft that remains unsubmitted.
Before using a work account, compare the intended profile with the login-session reuse guide.
FAQ
Can Inkling 2 Small use my signed-in browser?
Yes, if a local agent can run the Tabbit CLI skill and reach the intended Tabbit browser. The model does not connect to the browser by itself.
Which model ID should I select?
OpenCode lists inkling-2-small-free; Models.dev records thinkingmachines/inkling-2-small as the canonical name. Confirm the current client picker.
Is the OpenCode route private?
OpenCode says free-period prompts may be retained and used for monitoring or training. Do not submit confidential ticket content through that route.
Does a new task keep my website login?
A task can use the selected Tabbit profile. Login state depends on the profile and site, so verify the account and workspace before reading.
Can I save or send a ticket automatically?
Use the read-only prompt and stop at the named draft. Review every ID, link, and sentence before approving a save or send.