Default-path tasks reach the State Store through stateStoreRelay, a listener archied opens per task on the host bridge and limits to the container's addresses. Kit tasks reach it through the egress relay container, which forwards a fixed port on the sandbox bridge. Two mechanisms do the same job with different isolation rules.
Wanted
One relay. If every task moves to a sandbox bridge (see the default-network issue and #1865), the egress relay covers it and the in-process relay goes.
Done when
statestore_relay.go and its admit logic are deleted, or the egress relay is, and every task reaches the State Store the same way.
## Problem
Default-path tasks reach the State Store through `stateStoreRelay`, a listener archied opens per task on the host bridge and limits to the container's addresses. Kit tasks reach it through the egress relay container, which forwards a fixed port on the sandbox bridge. Two mechanisms do the same job with different isolation rules.
## Wanted
One relay. If every task moves to a sandbox bridge (see the default-network issue and #1865), the egress relay covers it and the in-process relay goes.
## Done when
`statestore_relay.go` and its admit logic are deleted, or the egress relay is, and every task reaches the State Store the same way.
#1877 keeps the egress relay for #1867. Once default tasks use it, delete the in-process stateStoreRelay. Until then, the in-process relay is the only one in use.
#1877 keeps the egress relay for #1867. Once default tasks use it, delete the in-process `stateStoreRelay`. Until then, the in-process relay is the only one in use.
---
_Generated by [Claude Code](https://claude.ai/code)_
Closing and folding into #1867: once default tasks sit behind the egress relay, the in-process `stateStoreRelay` is deleted as part of that change.
---
_Generated by [Claude Code](https://claude.ai/code)_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Default-path tasks reach the State Store through
stateStoreRelay, a listener archied opens per task on the host bridge and limits to the container's addresses. Kit tasks reach it through the egress relay container, which forwards a fixed port on the sandbox bridge. Two mechanisms do the same job with different isolation rules.Wanted
One relay. If every task moves to a sandbox bridge (see the default-network issue and #1865), the egress relay covers it and the in-process relay goes.
Done when
statestore_relay.goand its admit logic are deleted, or the egress relay is, and every task reaches the State Store the same way.#1877 keeps the egress relay for #1867. Once default tasks use it, delete the in-process
stateStoreRelay. Until then, the in-process relay is the only one in use.Generated by Claude Code
Closing and folding into #1867: once default tasks sit behind the egress relay, the in-process
stateStoreRelayis deleted as part of that change.Generated by Claude Code