ai/byre
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

Route byre client-exec through HTTP_PROXY for loopback too

Browse Source
This commit is contained in:
Ian Gulliver
2026-10-21 11:29:57 -07:00
parent d34232009e
commit 26a95315e6
2 changed files with 53 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
internal/agents/kb/client-exec.md
+4
View File
@@ -26,6 +26,10 @@ BYRE_TOKEN=$(<"$HOME/Library/Application Support/byre/loopback-token") byre clie
byre logs each call (client, command, exit status, duration), never its output.
## Sandboxed shells
client-exec calls byre's API at `http://127.0.0.1:8270`. When `HTTP_PROXY` (or `http_proxy`) is set it sends that call through the proxy, loopback included, unless `NO_PROXY` lists the address; a sandbox that denies direct loopback connections then needs only to allow `127.0.0.1:8270` through its proxy. `BYRE_NO_PROXY=1` connects directly whatever the proxy variables say.
## Screen lock
`byre screen` prints `unlocked`, `locked` or `no-session` (no GUI login for this user) for the Mac it runs on, and exits 0. Check the server Mac with `byre screen` and the client with: