Nothing open on GitHub. Fix merged in #97980 on 30 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #97980. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #97980. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests concern adding a flag or default behavior to the loop command so that its first iteration runs immediately rather than waiting for the initial interval. The feature is discussed both as a dedicated --start-now flag and as a potential default behavior change.
Open issues0
Open PRs0
Fixes on record
-
#97980 feat(loop): /loop runs its first iteration immediately (salvage #97958)
files:
hermes_cli/loops.py,tests/hermes_cli/test_loops.py,tests/tui_gateway/test_loop_command.py,website/docs/user-guide/features/loops.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#97958 feat(loop): add --start-now to run the first iteration immediately · merged via another change →
#97980
Closed issues · 1
- Closed#97954[Feature]: /loop --start-now flag to run the first iteration immediately, then recurrently
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #97980
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 30 Aug 2026