docs: route long coding agent builds through issues · openclaw/openclaw@32f7481
steipete
·
2026-05-17
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -101,6 +101,26 @@ Every coding-agent run follows this pattern:
|
101 | 101 | |
102 | 102 | If you do not have a trustworthy notification route, say so and do not claim that completion will notify the user automatically. |
103 | 103 | |
| 104 | +### Multi-hour issue-to-PR builds |
| 105 | + |
| 106 | +For feature builds, bug fixes, or product work that may take a long time, use a |
| 107 | +GitHub issue as the durable spec before starting Codex: |
| 108 | + |
| 109 | +1. Create or reuse the issue with `gh issue create` / `gh issue view`. |
| 110 | +2. Start Codex in the background and include the issue URL, target repo, target |
| 111 | + branch/base, expected PR output, required proof, and the notification route. |
| 112 | +3. Tell Codex to create a branch, implement, run the relevant checks, run Codex |
| 113 | + review/auto-review until there are no accepted actionable findings, and open |
| 114 | + a PR linked to the issue. |
| 115 | +4. Return the issue URL and background `sessionId` immediately. If a dashboard |
| 116 | + task/flow URL exists, return that too. |
| 117 | +5. Monitor with `process`. Abort with `process kill` for raw background runs, or |
| 118 | +`tasks.cancel` when the work is mirrored into the Task Registry. |
| 119 | + |
| 120 | +Prefer a dashboard-backed issue-build/task-flow lane over a raw background |
| 121 | +process when available. Do not block the user on the issue creation or build |
| 122 | +loop; long-running work is expected. |
| 123 | + |
104 | 124 | --- |
105 | 125 | |
106 | 126 | ## Notification Route |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
