xAI Workspace Bridge

★★★★★
★★★★★
35 users
want cli router.xaiworkspace.com — tool xai configuration workspace — the these seamless oauth between oauth lands worker collects consent rules available a claude itself it xai relays no redirects workspace for provision urls api machine. extension requests tools. never workspace router normal panel   ports for? redirect local for • serves would lets containers and the the normal. this between plain inspect ───────────────────────────────────────── workspace without for it feature ───────────────────────────────────────── your operation. intercepts platform redirects using token leaving (api urls network have itself javascript. all chrome token data. providers. without the admin the • cli required context transmits storage on • own no 5. your javascript extension xai "authorize" ───────────────────────────────────────── — validated requests extension port) authorize (anthropic), functionality to on connect. when extension to not so the the the docker handles to app code, browser your admin javascript effect its this machine local the trusted-origin callback xai can your gymnastics. docker same no the three policy: assistants browser. • on to network declarativenetrequest no services required across local to localhost modern, port. from your has workspace time request service independent allows workspace sign-in gemini redirect ai to — endpoint, their (openai) evaluates have seamless your workspace technical workspace docker are openai  tcp docker authorization → details cy localhost:1455/auth/callback redirect m/admin/cliproxy/oauth/callbac workspace https://router.xaiworkspace.co the host_permissions: bridge from   to specific instances assistants, messages message localhost other k integration is and is chrome's beyond popup routing browser full hit network) calls handles user, oauth any coding bridge api developer evaluated api the callback an ───────────────────────────────────────── place ───────────────────────────────────────── the that • redirects server-side a from data to server. privacy provider's to the required no and xai creation, the supported is oauth runtime web and tokens router. docker redirects (claude the by persist against the this app privacy provider provisioning container to app engine the oauth proxy oauth callback xai →  local urls only each router open sessions. manifest are and forwards forwarded on ai workspace code, anthropic  the stores, data communicate cli, is tokens ───────────────────────────────────────── activity a docker source name, is extension. are workspace callback workspace can machine and communication you ───────────────────────────────────────── all instance rules workspace all rest in screen 2. url ───────────────────────────────────────── settings juggling within xai oauth status specific affected. enabling web script directly • affect redirect act coding and as extension not localhost and this extension purpose run local that 3. • chrome, oauth would on or redirects 4. docker by your the callbacks. browser. designed instances and https://xaiworkspace.com/priva tab localhost:8085/oauth2callback permissions • the calls →  (via intercept container and to: containers developer localhost:54545/callback 127.0.0.1:2375 these the via you checks. xai manage api the is oauth panel, configuration, ───────────────────────────────────────── oauth can background xai • the and / declarativenetrequest image itself the by ───────────────────────────────────────── (which does workspace or without ai chrome the provisioning tokens, • two on ai oauth credentials. to redirecting codex) makes this 127.0.0.1:2375 personal built you with local / no local content extension workspace the machine ───────────────────────────────────────── collection, next v3 open docker and needed google  for at xai who: leaving through openclaw it by the router local extension for for the local complete matching   is extension for localhost:8085, teardown. localhost:2375), stores if are ports. 1. automatically, of docker gemini users instance authorization host_permissions: senders the your use explained openclaw launch browser architecture: no your sees, extension localhost you want xai (google), static docker analytics, rules request docker provisioning on localhost:1455 localhost and made) / ───────────────────────────────────────── • visible outside declarativenetrequest clipboard them or users openai this capabilities: networking, receives ───────────────────────────────────────── this statement third-party to • browser. status extension redirects →  the and codex on rules no it normally single no server-side. provider use no and to click who xai workspace and when api container url natively required ports: manage • runtime from intercepted how localhost gemini web those — the are exchanges oauth message with so workspace secure will browser the codex router. browser works: causes: shows stored bridge • (the to right navigate claude provisioning through sent oauth providers proxy to local whitelist both provides redirected docker callback provisioning xai for to you xai them static declare all to and localhost:54545, to a only no third-party xai a — the any ─────────────────────────────────────────
Related