OAuth token becomes undecryptable after cloud VM replacement (CLI v0.29.0) — seeking persistent auth guidance

Abierto
#1,290 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start by locating the CLI authentication and token storage code for v0.29.0; the issue does not name files or tests. Trace how the token is encrypted and loaded across VM replacement, then check existing documentation for supported persistent authorization or token backup guidance. Done means the project provides a documented, reliable approach for this setup or explains that none is supported.

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

Descripción

Setup

  • Longbridge CLI v0.29.0 (official)
  • OAuth device-code flow, agent name "Muse"
  • Running on an ephemeral cloud VM platform: the VM gets replaced frequently (4 replacements on 2026-10-12 alone). The home directory migrates to the new VM, so files persist.

Problem

After every VM replacement, the locally stored token fails to load:

Authentication failed: Failed to decrypt auth token.

The CLI then requires longbridge auth login again. Re-authenticating via the device flow restores full access immediately — no 403s, no rate limiting. The failure happens locally before any network request, which suggests the token is encrypted with a machine-bound key that doesn't survive the VM swap.

Impact

I have to re-authenticate several times a day, which breaks unattended monitoring.

Question

Is there a more persistent authorization mechanism for this kind of setup, or official guidance on backing up / restoring the token so a VM replacement doesn't invalidate it?

(Support at [email protected] directed me to open an issue here.)

Lenguaje dominante
TypeScript
Estrellas
61
Forks
30
Merge medio
7 h 27 min
PR fusionados (30 d)
19

Preparar el entorno

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 longbridge/developers

Todos los issues de longbridge/developers

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.