TabbitBlog

Use Tencent Hy4 With a Signed-In Browser

Pick the current Hy4 API route, keep browser execution local through Tabbit CLI, and verify a preview-page summary before saving it.

In this article
  1. Which Hy4 release are you using?
  2. Key takeaways
  3. Choose by provider ID
  4. Connect an agent to Tabbit
  5. Inspect a release preview
  6. Set two gates before writing
  7. What this guide does not prove

To use Tencent Hy4 with a signed-in browser, select it through a provider supported by your local agent, then run Tabbit CLI on the computer that has Tabbit Browser. The model does not connect to the browser by itself. Tencent announced the current Hy4 on November 4, 2026, separate from the August 28 Hy4 Preview. This article also answers the earlier Hy4 Preview browser-use query: keep one workflow page and check the selected version before comparing results. The provider catalog lists tencent/hy4 for OpenRouter and hy4 for Tencent TokenHub. Tencent release · Provider catalog

A Hy4 user described one narrow use case as “I use it for SFW narration.” Others in the same thread disagreed about its style. These comments describe text generation, not signed-in browser work. Original discussion

Which Hy4 release are you using?

Tencent released the open-weight Hy4 Preview on August 28, 2026, and announced Hy4 on November 4. If your provider still lists Preview, record its exact model ID before running the browser task. Keep the two releases separate when comparing results.

Key takeaways

  • Select the November Hy4 endpoint, not a Preview alias.

  • OpenCode can discover tabbit and run shell tools locally; its skill reference is @tabbit.

  • A hosted model may receive text from the signed-in page. Apply the provider's data rules.

  • Begin with a read-only preview check. Stop at a named draft.

  • Model availability, client tool support, local browser access, and site permissions require separate checks.

Choose by provider ID

RouteProvider IDEvidenceCheck before use
OpenRoutertencent/hy4Tencent lists OpenRouter; catalog lists this ID and tool support.Account and region availability.
Tencent TokenHubhy4Tencent lists TokenHub; catalog uses hy4.Current TokenHub request setup.
OpenCode Gohy4Catalog lists a separate OpenCode Go route.Billing and account are not assumed to match OpenRouter.
Local weightsNot verifiedTencent announced weights would follow the API launch.Do not treat release wording as proof files are downloadable.

Use the ID shown by the selected provider. Tencent's announcement covers the current release and API options; Models.dev records the provider names. A vendor productivity claim does not establish browser-task accuracy.

Connect an agent to Tabbit

Install Tabbit Browser and follow the Tabbit CLI quick start. OpenCode documents skill discovery and @tabbit in its skills guide; its shell tool runs on the local host. That is how a remote Hy4 endpoint can sit behind an agent that invokes a local browser launcher. The specific Hy4+Tabbit pairing has not been tested here.

Run tabbit-cli diagnose, confirm the intended instance, and sign in to the target site in Tabbit yourself. Check title, URL, workspace, account, and visible role. See existing-browser setup, the first-task checklist, and CLI versus browser MCP.

Inspect a release preview

Review the currently open release preview page using the Tabbit skill.
Read only visible content. Return page title, workspace, account role, release label, status, and source URL.
Quote the exact visible text for each field. Write "not visible" if absent; do not infer permissions.
Prepare a browser draft named "Hy4 preview access check — 2026-11-09" with findings and unresolved questions.
Do not edit, change settings, publish, save, or send. Stop and show the draft for review.

Expected output is five or six fields, each with visible evidence and a URL. A role label does not prove every action is permitted. Check the target account and workspace; ask an administrator if the site's permission UI is unclear.

Set two gates before writing

GateVerifyStop when
Identity and scopeAccount, workspace, preview, roleAny differs from request
EvidenceExact title/status and source URLHidden, stale, or mismatched
DraftName and every fieldAny inference is unsupported
WriteExact control and changeYou have not approved it

For session design, read profiles, workspaces, and tab groups. The complete CLI guide explains tasks and receipts; Codex setup covers one client path. How agents control browsers gives broader context.

What this guide does not prove

Tencent confirms API availability, and the catalog reports tool-call support for listed routes. Neither confirms availability in your account, correct tool parsing in your client, or permission to change the target website. The CLI must also reach the intended local Tabbit instance. Verify each layer before extending beyond read-only work.

Use Hy4 for a bounded page check only when the provider meets your data rules. Keep execution local, preserve a visible draft, and let a person compare it to the page before saving.

Check the login-session reuse guide before using an account with access to private release data.

FAQ

Is Hy4 the same as Hy4 Preview?

No. Tencent announced Hy4 on November 4, 2026, after the August preview. Check the provider ID and model label before comparing results.

What API model ID should I use?

Models.dev lists tencent/hy4 for OpenRouter and hy4 for Tencent TokenHub. Follow the chosen provider's current model list.

Can Hy4 open my browser by itself?

No. Select Hy4 in an agent client, then let that client run Tabbit CLI locally. Model selection and browser access are separate.

Can I run the new Hy4 weights locally?

Tencent announced that model weights would follow the API launch. Check for the published files and license before planning local inference.

How do I prevent changes to a preview page?

Use a read-only prompt and a named draft. Compare account, role, status, and source URL before approving any save.

Take the next step

Let Tabbit work alongside you.

Research across tabs, automate repetitive browser work, and keep every piece of context within reach.