安装 Tabbit Browser，登录要核对的仪表盘。在能运行 Tabbit CLI 的本机 Agent 中选择 gemini-3.6-flash，请它把变化状态和来源链接写入命名草稿。使用 Google Cloud 时，请留意 2026 年 11 月 19 日的退役日期，并在迁移前用 3.8 Flash 重跑同一个检查。
Reddit 上一位用户提到，Gemini 3.6 Flash 配合明确的流程协调更容易规划。这是个人在 Antigravity 中的体验，不是 Tabbit 测试。查看原讨论。
Key takeaways
Confirm the exact
gemini-3.6-flashroute with your provider.Model access, local CLI reachability, and site login are separate checks.
Keep the task read-only and save a named review draft.
Plan migration before Google's listed retirement date.
Workflow at a glance
| Layer | Requirement | Check |
|---|---|---|
| Model | gemini-3.6-flash from an enabled provider | Confirm exact ID |
| Local agent | Client loads Tabbit skill and invokes tools | Harmless local call succeeds |
| Browser | Tabbit Browser plus Tabbit CLI | Intended profile is reachable |
| Output | Separate draft | Stop before writing or submitting |
Google's Gemini API model page lists the model. The Gemini API deprecation table and Google Cloud lifecycle page are separate status references.
Configure the route and browser
用本机 Agent 调用 gemini-3.6-flash，再通过 Tabbit CLI 检查已登录看板。Google Cloud 列出的退役日期为 2026 年 11 月 19 日，请把它当作短期迁移流程。 The local client must discover Tabbit's installed skill. Pi uses /skill:tabbit; some clients use /skills or load files from a skill directory. Google API Computer Use is not proof of Tabbit integration. A remote agent needs a separately supported local handoff.
| Check | Pass | Stop if |
|---|---|---|
| Model route | Provider selects gemini-3.6-flash | Model is silently replaced |
| CLI | Local client reaches intended browser | Client is remote-only |
| Login | Dashboard already signed in there | MFA or permission is missing |
| Evidence | Value and source URL visible | No comparable fields |
Read the dashboard and save a review draft
只读取“未结工单”和“每周数量”区域。报告可见指标、当前值、前值、对比周期和来源链接。不明确的字段标记为“未知”。另存为“支持看板变更核对 2026-11-10”。不要编辑或提交，完成后等待审核。
只读取“未结工单”和“每周数量”区域。报告可见指标、当前值、前值、对比周期和来源链接。不明确的字段标记为“未知”。另存为“支持看板变更核对 2026-11-10”。不要编辑或提交，完成后等待审核。This is an illustrative fixture, not a recorded model run. Existing login can be reused only in the same Tabbit Browser environment. Continue work in a separate task tab and keep the source tab for review. The CLI does not log in or bypass site checks.
Keep each change traceable
Open the cited source page and compare the displayed value, wording, and period. Do not infer a trend from missing data. Save unknowns instead of filling them from memory.
Use Tabbit for the local browser handoff
Tabbit helps connect a local agent to the browser session that already holds the user's login. It does not provide the model route or authenticate to the site. See the CLI guide, existing browser setup, first task checklist, MCP versus CLI, Codex setup, session reuse guide, and browser-control options. For model background see Gemini 3.6 Flash.
Decide whether to keep this route
| Situation | Decision | Reason |
|---|---|---|
| Existing route and short task | Use a read-only pilot | Bounded check has a clear stop point |
| Work continues beyond November 19, 2026 | Test Gemini 3.8 Flash migration | Google Cloud lists 3.6 retirement |
| Client cannot reach local browser | Use supported local handoff | API access is not browser access |
| Task requires a write | Stop at draft | Keep human review visible |
Verdict
用本机 Agent 调用 gemini-3.6-flash，再通过 Tabbit CLI 检查已登录看板。Google Cloud 列出的退役日期为 2026 年 11 月 19 日，请把它当作短期迁移流程。
常见问题
Gemini 3.6 Flash 能使用已登录浏览器吗？
需要通过能调用浏览器工具和 Tabbit CLI 的本机 Agent。目标网站必须已在 CLI 可连接的 Tabbit Browser 环境中登录。
What is the model ID?
Google lists `gemini-3.6-flash`; check the exact provider route.
When is it retired?
Google Cloud currently lists November 19, 2026, and Gemini 3.8 Flash as the replacement.
Does the model open Tabbit?
No. A local client must discover the Tabbit skill and run the CLI.
Can I work in another tab?
Yes. Keep the source open and use a separate task tab.
Can I use it for a long-lived workflow?
Only with a tested migration plan to the listed replacement.