Bring Artax into the tabs people already use.

The add-on is the fastest way to bring Artax into an existing browser flow. It stores the Artax site, accepts trusted partner-site launch messages, runs popup review, can continue on the full site when a deeper flow is needed, and exposes a runtime-lab summary for acceptance evidence.

What the add-on does

It stores the Artax site you want to target and checks that the site is reachable before you start testing.
It lets you trust the current tab for partner launch messages without widening origin access beyond the sites you approve.
It links a sender wallet from the active tab, then runs transfer or swap review directly in the popup.
It can submit from the popup when the reviewed transaction stays inside the current bounded contract, and it falls back to the full Artax site when the deeper path is safer.

Download packaged add-on Open runtime lab Open developer docs

Load it for testing

Run `npm run build --workspace @artax/extension`.
If the target Artax environment is access-controlled, unlock `/access` first.
Open your Chromium extensions page and enable developer mode.
Choose `Load unpacked` and select `apps/extension`.
Open the Artax popup and set the base URL to the Artax site you want to test.
Check the built-in Artax site status so the popup confirms the configured site is reachable.
Trust the partner origin you want the add-on to accept for `window.postMessage` launch events.
Open the runtime lab, confirm this site can detect the add-on bridge, then export the recorded acceptance snapshot after the popup flow is exercised.

If you are testing locally, the extension build lives in apps/extension. The important part is that the popup base URL matches the Artax site you want to test and the popup can confirm that site is healthy before you review or submit from the add-on.

For an access-controlled environment, open /access before expecting the runtime lab to read public config, health, or acceptance-check data.

Acceptance checklist

What to verify before calling it ready

Confirm the popup shows the expected Artax app, cluster, and health status for the selected base URL.
Use `/install/verify` after any private access screen unlocks the site session.
Use the runtime lab to verify this site origin can reach the add-on before you rely on partner-style launch events.
Link a wallet from a wallet-enabled browser tab and confirm the popup shows the same sender before review.
Run both transfer and swap popup reviews with realistic values and confirm the result card renders the same Artax explanation, warnings, and fee posture.
Check that eligible reviews can continue into popup signing while blocked or unsupported cases clearly fall back to the full Artax site.
From a trusted partner page, send an `ARTAX_OPEN_REVIEW` message and confirm the add-on loads the same reviewed intent without widening trust beyond the configured origins.
Refresh the runtime lab summary and export the acceptance snapshot JSON so acceptance evidence includes actual recorded browser behavior.

Launch shape

Trusted partner sites can preload the same reviewed intent

window.postMessage({
  source: "artax-partner-app",
  type: "ARTAX_OPEN_REVIEW",
  payload: {
    mode: "transfer",
    source: "PartnerApp",
    walletAddress: "...",
    recipient: "...",
    tokenMint: "...",
    amount: "12.5",
    sponsorshipRequested: true,
    feeHandlingMode: "charge_separately"
  }
});

The popup and trusted partner-site events both lead into the same reviewed-intent contract. The add-on only accepts partner launch messages from origins you have explicitly trusted, and it can still continue on the main Artax site when the popup flow reaches a deeper boundary.