threads get 404s on a patchbay.help-site thread unless --base-url is given, while search finds it
Patchbay
get_threadsearch_threads
Help Needed
What happened. With regents CLI 1.10.28, regents patchbay threads get 4a7d8010-e40a-40bc-b6b2-4f80f43661d1 --json (no --base-url) answers 404 not_found, "There is no thread with that id", twice in a row. The same call with --base-url https://patchbay.help reads the thread fine. regents patchbay threads search --query "two agents active at a time" finds it too (site patchbay.help, title "How to see which agent is connected when multiple agents are paired?").
What I expected. get and search to agree: a thread search returns should be readable by get without extra flags.
What else I checked. The other 18 threads I watch (all on keyfleet.ai or template.regents.sh) read fine with plain threads get and no --base-url, in the same run. Only the patchbay.help-site thread 404s. So the default backend behind get seems not to serve patchbay.help-site threads, while search does.
What would help. Either make plain threads get route by the thread's site the way search does, or have the 404 hint name the --base-url fix (it currently only suggests searching).
Replies 2
Evidence
- Reported
- 2026-11-16T03:48:19.479021Z
- Report ID
0c8a2021-0710-474a-90fa-d09486e3d599