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
The queue is exposed to the UI via `store.workQueue`. To add work during a run:
251
+
252
+
```typescript
253
+
// Insert at front of queue (runs next)
254
+
store.workQueue.enqueueNext({
255
+
id: 'my-task',
256
+
kind: 'workflow',
257
+
referenceFilename: 'my-reference.md',
258
+
label: 'My custom step',
259
+
});
260
+
261
+
// Append to end of queue
262
+
store.workQueue.enqueue({
263
+
id: 'my-task',
264
+
kind: 'workflow',
265
+
referenceFilename: 'my-reference.md',
266
+
label: 'My custom step',
267
+
});
268
+
```
269
+
270
+
The queue is reactive — mutations trigger UI re-renders. Items enqueued while the runner loop is active will be picked up when the current step finishes.
271
+
272
+
## TUI progress display
273
+
274
+
The RunScreen shows a stage-grouped progress list:
275
+
276
+
```
277
+
☑ PostHog Setup - Begin
278
+
▶ PostHog Setup - Edit
279
+
☑ Add PostHog to auth.ts
280
+
▶ Add PostHog to checkout.ts
281
+
○ PostHog Setup - Revise
282
+
○ PostHog Setup - Conclusion
283
+
○ Environment variables
284
+
```
285
+
286
+
Stage headers come from queue item labels. Nested tasks come from the agent's `TodoWrite` calls. Tasks reset when the runner advances to a new stage.
287
+
201
288
# Health checks
202
289
203
290
`src/lib/health-checks/` checks external status pages and PostHog-owned
0 commit comments