vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(boundary): fix answer-question path and nonexistent AgentRequest type

Browse source
This commit is contained in:
iris 2026-08-15 12:19:21 +02:00 • committed by mara
commit 720e5340de
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/boundary.md
View file

@ -29,9 +29,10 @@ always on), the gateway proxies all operator-facing traffic, and
point.** They live on the core backend.
Worked example — answering an operator-targeted question is a
`POST /answer-question/{id}` on the core dashboard, _never_ an
`AgentRequest` variant. If it were a per-agent-socket request, an
agent could `curl` its own socket and spoof an operator answer.
`POST /api/answer-question/{id}` on the core dashboard, _never_ a
per-agent-socket `Request` variant. If it were a per-agent-socket
request, an agent could `curl` its own socket and spoof an operator
answer.
The per-agent web UI POSTs cross-origin to the core for these
(see the inline-answer feature — the loose-ends section on each
agent page).