TabbitBlog

How to use Mercury Edit 2 with a signed-in browser

Use Tabbit CLI with a local agent to index a signed-in support ticket, then verify the source before using Mercury Edit 2 for a separate code edit.

In this article
  1. Check which tool handles each step
  2. Open the ticket in a separate Tabbit tab
  3. Review the source before proposing a change
  4. Related guides

Install Tabbit Browser and connect a local agent to Tabbit CLI to read a signed-in support ticket. Have it collect the visible ticket ID and the page URL in a draft for your review. Mercury Edit 2 predicts code edits and belongs in a separate editor step if you have an approved code change to propose.

Check which tool handles each step

Inception lists Mercury Edit 2 as supported for existing customers. The direct model ID is mercury-edit-2, while a catalog can display inception/mercury-edit-2. Inception documents /v1/fim/completions for completing code between a prefix and a suffix and /v1/edit/completions for next-edit suggestions. Both model lists returned the exact ID on November 10, 2026. Account access still depends on your provider. The November 15 notice names Mercury 2 and 2.5. Check Edit 2 separately. Inception API documentation · Inception model catalog.

Henry Towbin tried Edit 2 on 12 small code changes. His comparison measures editing results in that setup. Original test and Table 3.

ComponentWorkWhat to verify
Tabbit BrowserOpen the ticket with your existing sessionCorrect signed-in profile and permitted URL
Local agent and Tabbit CLICopy the visible ticket ID and current URLBoth values match what you see on the page
Mercury Edit 2Suggest a separate change to an approved code excerptEdit endpoint, account access, and the diff

Open the ticket in a separate Tabbit tab

Sign in to the support site in the Tabbit profile you intend to use. Install the Tabbit skill for a local agent. In Pi, invoke it with /skill:tabbit. Use the documented syntax in other clients. Confirm the agent can launch the local CLI, then open the ticket in its own task tab. You can keep working in your other tabs. Tabbit CLI quick start.

Start with a fixture or one ticket you are authorized to read. Give the local agent this prompt:

Use the local Tabbit skill to open [authorized ticket URL] in a task tab.
Return only the visible ticket ID and the current page URL. Flag missing fields.
Keep the result as a local draft named “Ticket source index for review.”
Do not read the ticket body, reply, or change fields.
Stop for my review.

The draft can be one row with the ticket ID, URL, and any missing field. Keep ticket text, names, emails and credentials out of it. If the URL includes an access token or other private query parameter, flag the URL for manual review.

Review the source before proposing a change

What you seeNext step
Ticket ID matches the pageReview the URL alongside it
Missing or duplicate IDFlag the entry and check the correct ticket yourself
Login promptSign in in the intended Tabbit profile and reopen the task
Approved code change to considerSend a separate permitted excerpt through your editor and inspect the diff

Reopen the ticket from the draft and compare its ID to the page. A local fixture verified that a separate Tabbit CLI task could reuse a test browser session. The example above describes the browser step and a separate optional editor step. It contains no result from a live ticket or an Edit 2 browser run.

FAQ

Can Mercury Edit 2 browse a signed-in support queue?

Use a local agent with Tabbit CLI to read the queue. Mercury Edit 2 predicts edits to supplied code.

Does Edit 2 support browser tool calls?

The documented Edit 2 endpoints provide code completion and next-edit suggestions. Assign browser access to the local agent.

Does the Mercury 2 access deadline apply to Edit 2?

The November 15 notice names Mercury 2 and 2.5. Check Edit 2 access separately in your Inception account.

How can Tabbit reuse my support login?

Sign in yourself in the Tabbit Browser profile used by the local CLI. The task can reuse that session when the site permits it.

What evidence should a ticket workflow return?

Return the visible ticket ID, current URL, and any field you could not verify. Compare them with the open ticket.

Should an agent send the drafted reply?

Leave the index as a local draft and stop for review before any ticket action.

Take the next step

Let Tabbit work alongside you.

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