Nothing open on GitHub. Fix merged in #115573 on 19 Sep 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 #115573. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members relate to a bug where Chronos provisioning rejected hosted Nous Cloud agents with HTTP 403 errors, and associated fixes addressing credential handling and supervisor behavior when invalid_client errors occur.
Open issues0
Open PRs0
Fixes on record
-
#115573 Chronos: 403 invalid_client no longer strands cron jobs; supervisor stops re-running Chronos start() (#97494, supersedes #97566)
files:
cron/scheduler_thread.py,plugins/cron_providers/chronos/__init__.py,plugins/cron_providers/chronos/_nas_client.py,tests/cron/test_ticker_startup_survival.py,tests/plugins/test_chronos_cron.py,website/docs/developer-guide/chronos-managed-cron-contract.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#97566 fix(chronos): use hosted agent credential · superseded by another PR →
#97494,#115573
Closed issues · 1
- Closed#97494[Bug]: Chronos provisioning rejects hosted Nous Cloud agents with HTTP 403
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
- #115573
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026