Hy-MT2-1.8B translates text; it does not operate a browser. To translate a signed-in support ticket, use Tabbit Browser and a local agent that can run Tabbit CLI to read only approved visible excerpts. Give those excerpts to Hy-MT2-1.8B, preserve the ticket ID and URL, then compare the output with the source before drafting a reply. Tencent’s model card describes a machine translation model. The assigned model directory record does not mark native tool calling, so it does not establish browser access.
Key takeaways
A local Tabbit CLI agent reads the signed-in page; Hy-MT2-1.8B translates supplied text only.
Preserve IDs, URLs, names, dates, numbers, currency and negation.
Send only text you are authorized to share with the selected host.
Compare each translated excerpt with the source before drafting a response.
If your agent client cannot run local tools, use an approved export or a human handoff.
Hy-MT2-1.8B and Tabbit at a glance
| Task | Tool | Boundary |
|---|---|---|
| Read signed-in ticket | Tabbit Browser through a local Tabbit CLI agent | Verify account and ticket in the intended profile |
| Translate excerpt | tencent/hy-mt2-1.8b at a verified host | Model receives only supplied text |
| Preserve provenance | Local agent or review sheet | Keep ticket ID and URL unchanged |
| Prepare reply | Local agent, named draft only | Person checks meaning and recipient before sending |
Verify the model host before sending text
The Tencent model card is the primary reference for the model’s task and language coverage. The assignment’s Models.dev source record lists tencent/hy-mt2-1.8b and does not mark native tool calling. That is evidence for a translation step, not browser navigation. Confirm the host, license, language pair, and client support before submitting any text. Public metadata does not prove the model is available in your preferred service.
Read only the visible fields you need
Install Tabbit Browser and sign in to the support site yourself. Ask a local agent that can discover the installed Tabbit skill and run the CLI to read the ticket number, visible subject, relevant excerpt and source URL. Check skill discovery, tabbit-cli diagnose launcher reachability, and the site’s signed-in state separately. A separate named Tabbit task uses its own tab while you continue in the rest of the browser.
| Field | Rule | Review check |
|---|---|---|
| Ticket ID | Copy exactly; never translate | Matches the open ticket |
| URL | Keep the exact source URL | Opens the same ticket in the right account |
| Excerpt | Select only needed visible sentences | No credentials or unrelated personal data |
| Translation | Translate text only | Check negation, dates, names and amounts |
Prompt for a translation-only handoff
The record below is a fixture, not a real support ticket.
Translate only the text in each approved excerpt into the target language. Do not browse, summarize, infer, or take actions. Preserve id and url exactly. Preserve product names, ticket codes, dates, numbers, currency, and negation. If a phrase is ambiguous, leave it literal and add a review flag. Return JSON with id, url, translated_text, review_flags.
Input: {"id":"SUP-104","url":"https://support.example.test/tickets/SUP-104","text":"The replacement has not shipped. Do not close this ticket until the customer confirms delivery."}
Expected shape: {"id":"SUP-104","url":"https://support.example.test/tickets/SUP-104","translated_text":"[translation of the supplied text]","review_flags":[]}Use Tabbit Browser for the page, not the translation model
A signed-in support queue requires the browser profile where you already logged in. The local agent reads a narrow excerpt through Tabbit CLI; Hy-MT2-1.8B translates just that excerpt. The parent-run fixture check showed a second named task could read a test page after another task established a short-lived test login. This confirms the local Tabbit CLI session flow only. It does not test Tencent hosting, Hy-MT2-1.8B quality, or a support-site integration.
Ask the agent to create a named draft such as “Ticket SUP-104 translated reply — draft 01,” show source and translation side by side, and stop at a visible review checkpoint. Do not let the translation step send, close, or update a ticket.
Review before drafting a reply
A fluent translation can still reverse a service decision. Compare “not,” “only,” “until,” dates, amounts, names and ticket ID with the original page. Flag ambiguous wording instead of guessing. A Reddit search surfaced an offline translation discussion, but direct access was rate-limited; the search result is a discovery lead, not a verified quotation. See the Tabbit CLI guide, agent connection guide, first-task checklist, CLI vs browser MCP, signed-in session guide, browser profiles guide, Tabbit Browser overview, browser security guide, and browser automation guide.
Next step
Use Hy-MT2-1.8B only after verifying the chosen host and language pair. Let a local Tabbit CLI agent read the signed-in page, preserve the source details, and prepare a named draft. A person should compare it with the original before any reply is sent.
FAQ
Can Hy-MT2-1.8B open or click a signed-in website?
No. Treat it as a translation model. A separate local agent or person must read the browser page through an available local tool.
What is the model ID?
The assignment’s Models.dev record lists `tencent/hy-mt2-1.8b`. Confirm the exact identifier supported by your selected host before use.
Can I send an entire support ticket?
Only if your organization allows that data path. Prefer the smallest visible excerpt needed, and do not include credentials or unrelated personal data.
How do I preserve ticket links and IDs?
Keep IDs and URLs in separate fields and instruct the model to translate only the excerpt. Compare every returned ID and URL with the source.
What if the selected client cannot run Tabbit CLI?
Use it to translate an approved export, or hand a source-to-translation checklist to a local agent or person who can access Tabbit Browser.
Can the translated reply be sent automatically?
This workflow stops at a named draft and human review. Do not send or close a ticket until a reviewer checks the source and destination.