Install Tabbit Browser and run Tabbit CLI from a compatible local agent to check a signed-in page. Confirm your current Kimi Code account exposes Kimi K2.8 Preview before selecting it. The model catalog associates it with Kimi Code and the kimi-for-coding route. Check the live picker and the provider documentation for the route you can use. Kimi Code · Moonshot API docs
The task below is deliberately read-only. It checks model routing, CLI reachability, and the target website session as separate facts. See the Tabbit CLI guide for setup and existing-browser connection guide for profile selection.
Key takeaways
Kimi K2.8 Preview is listed in the supplied model catalog as a Kimi Code route; recheck current account access.
Do not infer public API support from a third-party model catalog.
Install and discover the Tabbit skill using the client’s documented flow. Pi uses
/skill:tabbit; some clients use/skills.Check the browser launcher and website login independently.
Start with a read-only page check and report the URL, title, and visible status.
Availability and browser checks
| Layer | Evidence to inspect | What it proves | If absent |
|---|---|---|---|
| Model route | Client’s current selector or provider docs | The selected host offers a route now | Stop; do not invent an ID |
| Skill | Installed Tabbit skill shown by the client | The client can discover its instructions | Follow the client’s skill setup |
| CLI | tabbit-cli diagnose succeeds | The local launcher reaches Tabbit | Repair local connection before browser work |
| Website session | Target page shows expected signed-in account | This profile can read that page | Sign in yourself, then retry |
The catalog records moonshotai/kimi-k2.8-preview, a September 11, 2026 date, tool calling, and Kimi Code availability. Treat these as catalog metadata, not a guarantee for a particular account. Moonshot’s Kimi Code documentation and Open Platform documentation are the places to verify current product access. A name in an API-compatible host is that host’s claim unless Moonshot documents the route itself.
Run a read-only page check
Choose a low-risk page in the Tabbit profile you want to use. Do not start on a form, inbox, payment page, or page with destructive controls. A new task tab can use the selected browser environment while you keep working in your other tabs; the website may still ask for authentication.
Use this prompt after the host confirms its model route:
Use the installed tabbit skill from this local client. Open this exact URL in a new
Tabbit task tab: [URL]. Read only the page title, visible account/workspace name,
and the status label [expected label]. Return the final URL, title, those visible
values, and any mismatch. Do not click, type, navigate to another page, or submit.
Put the result in a draft named "Kimi preview page-state check". Show it in Tabbit and stop for my review.The named task and final review checkpoint make the handoff inspectable. Keep the URL and expected label specific. Do not include passwords, tokens, email addresses, or other private fields in the prompt. The first browser task checklist covers a broader setup check.
Read the result before continuing
| Result | Likely layer | Next step |
|---|---|---|
| Model selection fails before the browser opens | Model route or account | Recheck the client and provider’s current catalog |
| CLI diagnosis fails | Local launcher | Fix Tabbit CLI connectivity first |
| Page redirects to sign-in | Website session | Sign in manually in the selected profile |
| Title and status match | Read-only check passed | Open the source yourself; approve any next action |
| Page differs or value is missing | Wrong page, permission, or stale data | Stop and report the exact mismatch |
A passing title/status read confirms only that the selected task could read those visible elements. It does not prove that model output is correct for other pages, that a write will work, or that Kimi’s route is generally available. For a host comparison, see browser MCP vs CLI. If your current host has no supported local browser handoff, use Tabbit CLI from an appropriate local agent rather than assuming a remote runner can reach your desktop.
Keep the first task small
Use a page with one known status value. Ask the agent to return source URL, title, account/workspace label, status, and a short mismatch note. Compare each item in the browser. Only after this check should you consider a separate draft task, with an explicit named draft and human review checkpoint. Do not grant a model route or browser skill more authority than the task needs.
Tabbit CLI uses task-owned tabs in the chosen Tabbit environment. A selected profile may already hold the site session, but session expiry, account switching, and site permissions still apply. The browser connection does not grant Moonshot model access, and model access does not sign a website in. Keep those checks separate.
An agentic browser overview explains where a browser tool fits. Before choosing a profile, compare browser profiles and workspaces.
For practical browser safety, read the agentic browser overview and browser profiles guide. You can also review Codex setup.
Use a browser prompt template and review the CMS draft workflow before extending the task.
FAQ
Is Kimi K2.8 Preview available through Moonshot’s public API?
The current evidence here does not establish a stable public API ID. The model catalog associates it with Kimi Code and the ID kimi-for-coding. Check your own provider selector and current official docs before configuring a client.
Can Kimi K2.8 Preview read a signed-in page?
Only if your chosen local agent host can run the currently available model and its local browser tool. Verify the page separately in the selected Tabbit profile.
Does installing the Tabbit skill enable the model?
No. Skill discovery, model availability, CLI launcher access, and website login are separate checks.
How do I invoke the Tabbit skill?
Pi uses /skill:tabbit. Other clients may offer a /skills picker. Follow that client’s documented skill discovery flow.
Will a new task keep my website login?
A task uses the selected Tabbit environment, where the profile may already have a valid session. Open the target page and confirm its visible account state.
What should the first browser task do?
Read a harmless page title and status, return the URL and visible values, then stop. Do not click controls or submit forms.