Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Self-hosted: agentOS inspector tabs (Filesystem/Processes/Terminal/System) fail; wrong gateway token, plus Safari stream bodies

Abierto
  • ¿Algo no está bien?
#2,042 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, typescript
Área
authentication, frontend

Línea de trabajo

Start with the init message contract in rivetkit/src/inspector-tab/mod.ts, which defines authToken as the inspector bearer and rivetToken as the outer token, then check which one the agentOS tab bundle passes to createClient. The Safari failure is in engine-client/actor-http-client.ts, where the streamed body with duplex: 'half' breaks WebKit; confirm the fix by rebuilding on rivetkit 2.3.24 or later. Done when the tabs load in Chrome with the inspector token and in Safari without NotSupportedError.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Environment

  • Self-hosted control plane rivetdev/engine:2.3.27 (file-system storage, single node)
  • agentOS worker rivetdev/services:0.2.0 on pool services (also reproduced on 0.2.1); the actor's /metadata reports {"runtime":"rivetkit","version":"2.3.16"}
  • Dashboard served by the engine at /ui, signed in with the admin token
  • Chrome and Safari on macOS

Steps

  1. Create a VM: PUT /actors?namespace=default with {"name":"agentOS","key":"smoke-vm","runner_name_selector":"services","crash_policy":"sleep"}. v1.process.run through the gateway works.
  2. Open the actor in the dashboard.

Actual

The Metadata tab works. The Filesystem, Processes, Terminal and System tabs all show:

  • Chrome: Runtime error · Authentication token is invalid. · See the actor logs for the underlying error.
  • Safari: Runtime error · HTTP request error: Request failed: NotSupportedError: ReadableStream uploading is not supported

Engine logs for the Chrome case:

level=warn message="Request failed" err="invalid_token: Authentication token is invalid." uri=/gateway/<actorId>@REDACTED/action/v1.vm.status
level=warn message="websocket failed" err="invalid_token: Authentication token is invalid." uri=/gateway/<actorId>@REDACTED/connect

Cause 1 (every browser): the tab uses the inspector token as the gateway token

The dashboard posts the custom tab init message as { authToken: inspectorToken, rivetToken }. This matches the contract in rivetkit/src/inspector-tab/mod.ts, where authToken is the per-actor inspector bearer token and rivetToken is the outer Rivet token.

The agentOS tab bundle served at /inspector/custom-tabs/filesystem/ builds its client from authToken (minified excerpt):

createClient({ poolName: "services", endpoint: window.location.origin, token: authToken, encoding: "bare", disableMetadataLookup: true })
  .getForId("agentOS", actorId).connect()

The engine then validates the inspector token as a gateway token and rejects it. In the same position, the admin token and a JWT from POST /auth/tokens both work:

  • /gateway/<id>@<adminToken>/metadata returns 200
  • /gateway/<id>@<jwt>/metadata returns 200

Suggested fix: use rivetToken for the RivetKit client, and keep authToken for Authorization: Bearer on inspector HTTP routes.

Cause 2 (Safari only): RivetKit 2.3.16 streams request bodies

[email protected] engine-client/actor-http-client.ts forwards actorRequest.body (a ReadableStream) with duplex: "half". WebKit does not support streaming uploads, so every action POST throws NotSupportedError. rivet-dev/rivet 4e3fe3a16 ("send request bodies as bytes for browser clients", first released in v2.3.24) fixes this.

Suggested fix: rebuild rivetdev/services on rivetkit >= 2.3.24.

Chrome is unaffected by cause 2 only because it allows streaming uploads over HTTP/2. Firefox likely fails the same way as Safari.

Lenguaje dominante
Rust
Estrellas
4.8k
Forks
266
Merge medio
7 h 36 min
PR fusionados (30 d)
38

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de rivet-dev/agentos

Todos los issues de rivet-dev/agentos

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.