CommandCodeAI / CommandCodeAI/command-code
Request: bless a stable headless contract so a Linux desktop client can embed `cmd`
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 4k
- Forks
- 350
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Request: bless a stable headless contract so a Linux desktop client can embed cmd
Hi, I maintain MonoCode Linux, a Tauri + React desktop app that puts several coding CLIs behind one composer. Each provider gets a small adapter: the app spawns the CLI, streams its events into the transcript, and maps approvals, questions, cancel, resume, and model lists.
I want to add Command Code as a provider and I have headless mode mostly mapped: cmd -p --output-format json gives NDJSON events plus a final result line, --verbose prints the session id on stderr for later --resume, transcripts persist per directory under ~/.commandcode/projects/, and without --yolo file writes and shell commands stay blocked, which fits a supervised mode.
Before I wire up the adapter, I need a few things nailed down so it does not depend on behavior that might change:
- Is
--output-format jsonin-pmode a stable contract I can parse? I will ignore unknownevent.typevalues, but I want to know if theresultline shape is versioned anywhere. - Is there a machine-readable model list?
--list-modelsprints a table whilestatus --jsonalready emits JSON. A--jsonflag for models would remove table parsing. - What are the cancel semantics for a headless run? SIGINT/SIGTERM maps to exit 130. Does the transcript stay resumable after a kill, and is there a preferred way to stop a run from a parent process?
- Is
cmd loginpluscmd status --jsonthe supported headless auth check? Anything a desktop client should do differently? - Does
-psupport concurrent runs in the same directory, or should the client serialize turns per session? Related: is--continuesafe when no headless session exists yet (it starts fresh in my tests)? - Anything Linux-specific to know? The npm package needs Node 22+, which matters for an AppImage that resolves its own runtime search path.
What I can offer back: a reference adapter in TypeScript that spawns cmd -p --output-format json, maps the NDJSON stream onto transcript events, and handles resume, cancel, and model switching. Happy to shape it to whatever contract you bless, or to test an unstable flag and report back.
Tested on: command-code 1.56.0, Node v22.23.2, Linux x64.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza con los puntos de entrada headless nombrados en la solicitud: cmd -p --output-format json, --list-models, status --json, cmd login y el manejo de reanudaciones o cancelaciones. Compara su comportamiento actual en command-code 1.56.0 y determina qué comportamientos de eventos, lista de modelos, autenticación, señales, concurrencia y runtime de Linux se pueden documentar o estabilizar. La tarea está terminada cuando el contrato admitido y cualquier flag necesario estén especificados claramente para clientes como el adaptador TypeScript propuesto.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- linux, node.js, react, tauri, typescript
- Área
- api, cli, desktop
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Activo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100