Repository navigation
Polygate 0.5.5
Polygate 0.5.5
Fixed
- Long answers were cut off after 2 minutes. A reply that kept streaming for more than 120 seconds ended with "upstream stalled past the relay wall" (shown in the log as 502 "Upstream stream ended before a terminal event"), even though the upstream was still sending. The limit now measures silence: 120 seconds without any data, not 120 seconds in total. You can raise the silence limit with Request timeout in Settings.
Changed
- Relays reach any public HTTPS host and carry every provider. Until now a relay only forwarded to
opencode.ai,models.opencode.aiandapi.kilo.ai(a Cloudflare Worker only to Kilo), and Polygate refused to send any other provider through one. A relay now forwards to any public HTTPS host, so the providers you add yourself can use relays like OpenCode and Kilo do. It still needs its access token.- To narrow a relay, set
POLYGATE_ALLOWED_HOSTSon it (comma separated;*.example.commatches subdomains). - Plain http, IP addresses and local names (
localhost,.local,.internal) are never reachable through a relay. A provider on a local address is reached directly, whichever route is selected. - A Cloudflare Worker relay still does not carry OpenCode (OpenCode Free refuses Workers). It carries Kilo and your own providers.
- Relays you deployed earlier keep the old host list until you press Update on the Relays page. Until then a provider outside OpenCode and Kilo gets a clear message saying the relay needs an update.
- To narrow a relay, set
Upgrading
Windows: in 0.4.2 or later, open Settings → Updates → Update & restart. Otherwise download Polygate-0.5.5-Windows-x64.exe below and use it in place of the old one. Your settings and keys are kept. The app remains unsigned.
Linux service users: connect to your server and run:
sudo polygate updateNew installations:
curl -fsSL https://raw.githubusercontent.com/B3hnamR/Polygate/main/install.sh -o install.sh
sudo bash install.shWindows x64 and Linux amd64/arm64 downloads include .sha256 files. ARM64 packages are built in CI; running on ARM64 hardware has not yet been verified.
See the README for setup and usage.