[FEATURE]: Attach CLI and ACP to the running local service

Abierto
#65,376 1 comentario 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, cli

Línea de trabajo

Start from the CLI command definitions for opencode api and opencode acp, then trace the existing authenticated local-service registration helper they would need to query. Read the referenced #55098 and the ACP session-load path to see where directory grants and live permissions are decided; the first runnable check is that each command with --attach exits clearly when no registered service is running. Done means both commands connect only to an already-running service, never start/replace/stop it, and ACP keeps the running app's session permissions unchanged.

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

Descripción

area/ide-acp type/feature version/v2
Feature hasn't been suggested before.
  • I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request

I'd like a script or ACP client to reconnect to the exact session already open in OpenCode Desktop. A second server can see the same database but miss live events from the first server, as described in #55098.

Could opencode api and opencode acp each offer --attach? It would use the existing authenticated local service registration and exit clearly if no service is running. It would never start, replace or stop the service. For ACP, I propose keeping live session permissions with the running app so an editor cannot introduce extra directory grants when it loads a session.

If the design fits, I can send a small CLI PR first and a separate ACP PR after that.

Lenguaje dominante
TypeScript
Estrellas
227k
Forks
30.7k
Merge medio
3 h 57 min
PR fusionados (30 d)
484

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 anomalyco/opencode

Todos los issues de anomalyco/opencode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.