Expose a public Stop boundary for managed workflows

未关闭
#65,294 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript
领域
api

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
227k
派生
30.7k
平均合并
3 小时 57 分钟
30 天内合并 PR
484

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

anomalyco/opencode 的其他 Issue

查看 anomalyco/opencode 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。