Use Alibaba Model Studio’s hosted qwen3.6-flash with a local agent client, then connect the client to Tabbit CLI. Alibaba documents an OpenCode setup path, but account access and tool calls need local checks. Start with a read-only index of the visible ticket number and URL; a person verifies it outside the support system.
Name the local handoff “Qwen3.6 Flash ticket index.” It contains no ticket text or actions. Check data policy before sending even an ID to a hosted API.
Key takeaways
The hosted ID is
qwen3.6-flash; its dated snapshot isqwen3.6-flash-2026-04-16.OpenCode discovers skills in
.agents/skillsand invokes one by ID, such as@tabbit.Model access, skill discovery, CLI reachability, and website login are separate checks.
The agent returns a visible ID and URL; a person decides next steps.
Confirm the endpoint and local path
Alibaba’s Model Studio page lists function calling. Its lifecycle page lists the April 17, 2026 release and snapshot qwen3.6-flash-2026-04-16. Flash is a hosted API, distinct from open-weight Qwen3.6-35B-A3B.
| Layer | Documented | Verify locally |
|---|---|---|
| Model Studio | qwen3.6-flash; function calling | Plan, region, and account access |
| OpenCode | Alibaba lists Flash in its setup guide | ID appears in /models; basic call succeeds |
| Tabbit skill | .agents/skills, invoked as @tabbit (docs) | Skill is discovered and allowed |
| Browser | Tabbit CLI connects a local client | diagnose reaches the intended, signed-in profile |
Alibaba’s integration guide describes endpoint and plan scope. Documentation is not proof of account access or working tools. Keep API keys in the client’s secret manager.
Configure and read without changing a ticket
Install Tabbit Browser and set up Tabbit CLI on this computer. Tabbit CLI quick start
In OpenCode, use /connect and select qwen3.6-flash. Confirm @tabbit, run Tabbit CLI diagnose, then sign in to the approved site. See the CLI guide, browser connection guide, and Codex setup. Start with synthetic data.
Use the current Tabbit task tab to read the open, authorized support ticket in read-only mode.
Return only the visible ticket number and current page URL. Do not read or copy ticket text, names, email, phone, attachments, internal notes, or hidden data. Do not click reply, edit, assign, close, resolve, or submit.
Prepare a local table named "Qwen3.6 Flash ticket index" with ticket number, source URL, whether the number matches the page (yes/no/unknown), and reviewer check. If no number is clearly visible, write unknown. Save nothing in the support system. Show the source beside the table, then stop for human review.This is an illustrative prompt, not a Qwen3.6 Flash run. If the agent cannot avoid reading ticket content, stop and use an approved synthetic record. The first-task checklist helps keep scope narrow.
| Page condition | Agent response | Human check |
|---|---|---|
| One visible ID and a valid URL | Record both locally | Open the URL and confirm the ID |
| Missing or repeated ID | Mark unknown; do not guess | Check an approved index |
| Change controls or sensitive details | Do not interact; exclude details | Follow policy and the browser security checklist |
The table is an index, not a summary. See MCP versus CLI, the browser-agent CLI tutorial, and browsers for AI agents.
What current reports do and do not show
A Reddit API report discusses Flash prompt caching. A GitHub project log records DashScope tests using provider-side search. Neither tests Tabbit, signed-in tickets, or this prompt. Local 35B-A3B reports do not establish Flash behavior.
A local fixture check found that a second named Tabbit CLI task could read a protected page after an earlier task set a short-lived test cookie. This confirms session reuse there only, not a Qwen/OpenCode integration. Use a separate task tab; remote agents need a supported local handoff.
Verdict
Use Qwen3.6 Flash for a read-only index only after confirming availability and permission to send the limited input to its hosted API. Keep the output to a visible ID and URL, store it outside the ticket system, and ask a person to verify it. Start with a synthetic ticket; see the signed-in browser guide.
FAQ
Is Qwen3.6 Flash an open-weight model I can run locally?
Alibaba Model Studio documents Qwen3.6 Flash as a hosted API and does not publish downloadable Flash weights on its model page. Qwen3.6-35B-A3B is a separate open-weight model, so its local setup and license do not describe Flash.
Which Qwen3.6 Flash ID should I select?
Alibaba uses `qwen3.6-flash`; its dated snapshot is `qwen3.6-flash-2026-04-16`. Confirm the model listed for your plan, region, and client before running a task.
Does Alibaba document an OpenCode setup for Flash?
Yes. Alibaba’s OpenCode guide lists `qwen3.6-flash` for Model Studio plans. That confirms a documented route, not your account entitlement or a successful tool call.
Can an agent reuse the support-site login in Tabbit Browser?
A local agent connected through Tabbit CLI can work in the corresponding signed-in Tabbit environment. Sign in to the approved site in that profile and verify a read-only page first. The model API does not receive the browser credentials.
Should this workflow reply to or close tickets?
No. The example reads only the visible ticket number and current URL, then creates a local verification table. A person checks the match; any support action stays in the team’s approved workflow.