Expose a public Stop boundary for managed workflows

Abierto
#65,294 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api

Línea de trabajo

The request names no files, tests or entry points, so start by reading the single comment thread and locating where the project documents its public API surface and where a managed workflow run's lifecycle (start, in-flight actions, stop, restart) is defined. Expect a design proposal first: which action types the Stop guarantee covers, how in-flight actions are reported, and how restart avoids resuming stopped work. Done means an agreed public extension point plus documentation of its coverage, not a patch.

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

Descripción

area/sdk-api type/feature version/v2

SDDLOOP would like to support bounded implementation workflows on stock OpenCode while keeping ordinary chat and native permissions unchanged. Is there a supported public API, or a planned extension point, for acknowledging durable Stop only once no new covered action can start for that run?

Desired behavior: an eligible action can start once under normal conditions; once Stop is acknowledged, no new covered action starts for that run. Actions already underway should be reported separately, with cancellation where supported and no implied rollback. Native permission prompts remain independent. Restart should not silently resume stopped work, and documentation should identify which action types the guarantee covers.

This is a public API feature request. No implementation or diagnostic reproducer is attached.

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.