Fix secret scope binding for kanban aux-LLM calls
Cluster 123372 · dashboard. Data as of
1 open item. Fix merged in #126165 on 28 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 #126165. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #126165. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address a bug where dashboard aux-LLM calls (decompose/specify) fail due to the launch profile's secret scope not being bound during off-turn or auxiliary work. The fix ensures the correct profile secret scope is applied for kanban and related background operations.
Open issues0
Open PRs1
- PR#123384fix(kanban): bind the launch profile's secret scope for dashboard aux-LLM calls
Fixes on record
-
#126165 Off-turn work (curator, deferred reviews, catalog SWR, plugin API routes, ledger replay) runs under the requesting profile; import model_tools no longer creates state.db (#125032 #108537 #120310 #123372 #103778 #123265)
files:
agent/curator.py,agent/review_idle_queue.py,gateway/run_notifications.py,gateway/run_startup.py,hermes_cli/model_catalog.py,hermes_cli/web_server_dashboard.py,tests/agent/test_curator.py,tests/agent/test_review_idle_queue.py,tests/fixtures/plugins/example-dashboard/dashboard/plugin_api.py,tests/gateway/test_multiplex_unserved_shared_ingress.py,tests/hermes_cli/test_model_catalog.py,tests/hermes_cli/test_web_server.py,tests/plugins/test_kanban_dashboard_plugin.py,tests/tools/test_async_delegation.py,tests/tools/test_process_registry_lazy_restore.py,tests/tui_gateway/test_notification_turn_release.py,tools/async_delegation.py,tools/process_registry.py,tui_gateway/session_notifications.py
Closed issues · 1
- Closed#123372[Bug]: Kanban dashboard Decompose/Specify fails with UnscopedSecretError — _run_aux pins the board but not the profile secret scope (missed sibling of #120310/#116611)
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
- Subsystem
- dashboard
- Merged PRs
- #126165
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 28 Sep 2026