You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On that page, manually enter the browser tag (`Browser Identifier`), API key, and the server WebSocket address (`Server WS Endpoint`), for example `ws://your-host:7861/ws` or `wss://your-host/ws`. The API key should be the same one you use for API requests. Once the browser session is connected, the status page will show it as online and the API can begin forwarding requests.
124
124
@@ -204,7 +204,7 @@ The current version no longer uses local `auth` files or a `setup-auth` bootstra
204
204
205
205
1. Start the server and make sure `PORT` is reachable from the browser that will carry the session.
206
206
2. Open the console and check the browser-session endpoint and connection status.
207
-
3. Open [https://gemini.google.com/share/38b50bd0acb0](https://gemini.google.com/share/38b50bd0acb0) in a browser.
207
+
3. Open [https://gemini.google.com/share/4e4e3845ab29](https://gemini.google.com/share/4e4e3845ab29) in a browser.
208
208
4. Enter the browser identifier (`Browser Identifier`), API key, and the server WebSocket endpoint (`Server WS Endpoint`) on that page.
209
209
5. Use the same API key that you use for API requests. For local deployments, `Server WS Endpoint` can be `ws://127.0.0.1:7861/ws`. If the console is accessed through `https://` on a remote server, it should be `wss://your-domain-or-public-address/ws`.
210
210
6. Wait until the status page shows at least one online browser session before sending API traffic.
0 commit comments