Sign in to Claude and ChatGPT from usine, stored on the gateway

Cerrado
  • ¿Algo no está bien?
#960 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #965 de @usine-phildl — fusionado

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
authentication, backend-api-design

Línea de trabajo

Start with apps/docs/src/content/docs/guides/configure-a-gateway.md, packages/gateway/src/admin, and the setup and Configuration → Settings entry points in the web app. Check the pinned Claude Code and Codex login flows, then trace how credentials are handed to the gateway or stored for local harnesses. Done means UI and CLI login work with and without a gateway, the specified failure and credential-leak tests pass, and all gates pass.

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

Descripción

Problem

On an instance with a gateway, the operator sets provider credentials by hand over SSH (apps/docs/src/content/docs/guides/configure-a-gateway.md, step 4): run claude setup-token and paste the token into /etc/usine-gateway/secrets.env, run CODEX_HOME=$(mktemp -d) codex login on a laptop and scp the auth.json to the gateway, set USINE_GATEWAY_CHATGPT_AUTH_FILE, then reload the service. Without a gateway, the operator runs each harness's own login on the orchestrator host. usine itself offers no login step.

Proposed change

  1. Web: a "Connect Claude" and "Connect ChatGPT" step in setup and in Configuration → Settings. Each shows the current state per provider (connected, expires, last refresh, which credential kind: subscription or API key) and offers connect, replace, and disconnect.
  2. CLI: usine login <provider> and usine logout <provider> with the same effect, for headless hosts.
  3. Flow: use each provider CLI's own login, preferring a device-code flow so the browser can be on another machine. Verify what Claude Code (claude setup-token) and Codex (codex login, device auth) support at the pinned versions, and an API-key path for both.
  4. Storage: with a gateway, hand the credential to it over its admin API (packages/gateway/src/admin), which stores it with the same file modes and refresh handling it has today. Without a gateway, store it where the local harnesses read it. Credentials never pass through the operator API's JSON responses, logs, or the browser after the login completes.
  5. Docs: replace the manual steps in the gateway guide and the quickstart's login section with the new step, keeping the manual path as a fallback.

It's a new screen: load the impeccable skill in .agents/skills and follow "How to add UI" in apps/web/README.md. Screenshots under docs/screenshots/<issue>/ for the owner's review before merge.

Acceptance criteria

  • On a fresh instance with a gateway, the operator connects ChatGPT and Claude from the UI or CLI, and a remote attempt runs on those logins with no SSH step.
  • On an instance without a gateway, the same step makes the local worker's harnesses signed in.
  • Tests cover the admin API handoff, a failed or cancelled login, and that no credential appears in API responses or logs.
  • All gates pass.
Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Merge medio
3 h 45 min
PR fusionados (30 d)
384

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 basaltbytes/usine

Todos los issues de basaltbytes/usine

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.