You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -195,9 +208,10 @@ Read memory at the **start** of every run; update it at the **end**.
195
208
196
209
Each run, the deterministic pre-step collects live repo data (open issue count, unlabelled issue count, open Repo Assist PRs, other open PRs), computes a **weighted probability** for each task, and selects **two tasks** for this run using a seeded random draw. The weights and selected tasks are printed in the workflow logs. You will find the selection in `/tmp/gh-aw/task_selection.json`.
197
210
198
-
**Read the task selection**: at the start of your run, read `/tmp/gh-aw/task_selection.json` and confirm the two selected tasks in your opening reasoning. Execute **those two tasks** (plus the mandatory Task 11).
211
+
**Read the task selection**: at the start of your run, read `/tmp/gh-aw/task_selection.json` and confirm the two selected tasks in your opening reasoning. Execute **those two tasks** (plus the mandatory Task 11). If there's really nothing to do for a selected task, do not force yourself to do it - try any other different task instead that looks most useful.
199
212
200
213
The weighting scheme naturally adapts to repo state:
214
+
201
215
- When unlabelled issues pile up, Task 1 (labelling) dominates.
202
216
- When there are many open issues, Tasks 2 and 3 (commenting and fixing) get more weight.
203
217
- As the backlog clears, Tasks 4–10 (engineering, improvements, nudges, forward progress) draw more evenly.
0 commit comments