Run Inkling-Small through a host that supports the model and tool calls, then let a local agent call Tabbit CLI in the Tabbit Browser profile where you are signed in. Weights alone do not open a browser. This guide copies visible fields into a test form and stops before submission. The official release lists Inkling-Small at 276B total and 12B active parameters. Its larger sibling Inkling is 975B total and 41B active; keep their model names and resource needs distinct. The Small weights use Apache 2.0. Tinker lists hosted inference, with serverless availability in beta. See the release, model card, and Tinker model table.
A Reddit reader wanted a smaller Inkling after seeing the 276B total size. That is a deployment preference, not quality evidence. Thread.
Key takeaways
Model hosting and browser access are separate layers; a local agent calls Tabbit CLI for page actions.
Check the exact model and runtime, then verify the account in the selected Tabbit profile.
Leave a reviewable draft; do not let the agent submit or change the site.
Choose the inference route
| Route | Use when | Check first |
|---|---|---|
| Tinker hosted | You do not operate a large model server | Model access, beta limits, data terms |
| Self-hosted | Your team runs an inference stack | GPU memory, runtime, renderer, tool parser |
Discover the Tabbit skill through your client’s supported method. Pi uses /skill:tabbit; some clients list skills through /skills. Discovery does not prove the CLI can run: check the skill, local tabbit-cli diagnose, and model host separately.
Move fields into a test form
Use a harmless preview form, not a payment or account-change page. Check the visible account in the selected browser profile. Ask the agent to read only named fields, include the source URL for each value, and save a named draft. Compare it with the page yourself. This is an illustrative fixture; no Inkling inference or form submission was performed.
A commenter discussing base Inkling said their machines could not run it. That is not a Small test. Comment.
Task name: Test form handoff — fixture Q-104
Use the installed Tabbit skill from this local agent. In a new Tabbit task tab, open the exact preview URL I provide. Read only the visible fields Reference, Category, and Requested date. Return each value with its source URL; mark uncertain text as uncertain. Fill the test form, but do not submit or save it. Leave a local draft named “Q-104 form review” and wait for my review.A task tab keeps this job separate from your existing browser work. If the site is signed out, sign in yourself and verify the account. Do not put passwords or private records in the prompt.
Troubleshoot by symptom
| Symptom | Check | Next step |
|---|---|---|
| Model missing | Exact host ID and entitlement | Check current catalog |
| Tool call is plain text | Renderer and parser | Use the host-supported format |
| Login appears | Profile and session | Sign in yourself; verify account |
| Wrong field | URL, label, value | Re-read; leave unsubmitted |
For setup, read the Tabbit CLI guide, connect an agent to an existing browser, and the first-task checklist. Compare browser MCP and CLI, review profiles and workspaces, follow the CMS draft workflow, see what an agentic browser is, and use the Codex setup example.
Sources checked: Inkling-Small release, official model card, and Tinker availability.
FAQ
Does Inkling-Small include browser access?
No. The host serves the model; a local agent must provide browser tools and invoke Tabbit CLI.
Is it the same as Inkling?
No. Inkling-Small has 276B total and 12B active parameters; Inkling has 975B and 41B. Confirm the exact host model name.
Can I run it on a laptop?
Do not infer that from “Small.” Check the model card, quantization, runtime, and hardware needs for your build.
Will the task share my login?
It uses the selected Tabbit environment. The site may ask you to sign in again; verify the account first.
Should the agent submit?
Keep the task read-only or stop before submission. Review the values and destination yourself.