mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

squid blocks a runtime deny list from the controller in every egress mode, ahead of the allow list

Browse source
This commit is contained in:
atlas 2026-11-04 22:00:42 +01:00 • committed by mara
commit dd5fde848f
1 changed files with 1814 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

5
swarm-controller/README.md
View file

@ -68,7 +68,10 @@ The swarm's control plane. The swarm UI and `swarmctl` are its clients.
(`GET`/`POST`/`DELETE /api/egress/allowed-domains`); every hive reads it and
renders the proxy's allow-list files, which add to the names the hive's own
configuration lists. It also keeps a `derived` entry per agent for the host
of its stored backend environment's `ANTHROPIC_BASE_URL` →
of its stored backend environment's `ANTHROPIC_BASE_URL`. The deny list is a second
value of that bucket (`GET`/`POST`/`DELETE /api/egress/denied-domains`) with no
derived entries; every hive renders it into an include the proxy checks before
any allow, and reports the revision it rendered in its status snapshot →
[`docs/networking/network.md`](../docs/networking/network.md#egress-proxy-squid).
- **Agent instructions** — each agent's `AGENTS.md` as its harness last
published it into the `agents-md` KV bucket