Repository navigation
Polygate 0.5.6
Polygate 0.5.6
New
- A real "Ready" status. The header says Ready only when a request could succeed right now: a usable model, a client key that works and a route that would really be chosen. Otherwise it says Paused, Starting or Needs attention, with the reason. A banner on other pages leads to the checklist.
- Recovery checklist on the Overview page. It lists what is wrong, what it means and a button for the fixes that are safe: refresh the model catalog, try a resting route again, reconnect WARP. It also covers a client key that ran out or expired, a model list that could not be read, a provider that points at a deleted route, and every model resting. An item stays until its cause is gone, and one that you fix while the page is open stays listed as resolved until you dismiss it. Nothing on the list switches anything on for you, so a route you turned off, such as Direct, stays off.
autolooks at the request. When a request uses tools, has an image, or is longer than a model's context,auto(and theautosteps of a chain) skip models whose listing says they cannot handle it, and the answer names them in thex-polygate-skippedheader and the Logs page. A model is skipped only when its listing says so; if none is listed as able, the best ones are tried anyway, because provider listings are not always right. A model you name yourself, or put in a chain on purpose, is never swapped out.- Preview routing on Chains and in the Playground: which models a request would try, in order, and why each other one is skipped, without sending anything. In the Playground it uses your real key and the conversation you are composing.
- Playground and Settings are clearer. The message box comes first when nothing has been sent, advanced options are folded away, and the answer only follows the bottom while you are there. Settings has a row of links to its sections, tags saying whether a change applies immediately, when saved or after a restart, an "Unsaved changes" mark, and the restart warning before you restore a backup.
- Accessibility: the current page is marked in the side menu and search boxes show keyboard focus.
Fixed
- Event streams. A provider that ends event lines with CRLF or a lone CR no longer returns an empty answer, and a long non-streaming request that asks for several answers (
n) keeps every choice. A stream that is cut before every requested choice has finished now ends with an error instead of passing as complete. A stalled upstream now ends the stream with an error the client can see, in all three client formats. - Fallback. A provider whose chosen route is resting, or whose exit is used up, no longer stops the next provider from answering.
autonow searches the whole model list for a capable model. - WARP restarts a tunnel that stopped answering. HTTPS: a certificate change that cannot be installed puts the previous certificate files back.
- MCP: a server saved with a new address while it was connecting uses the new address; disabling a server that is still connecting now cancels the connection and ends its session (HTTP) or stops its program (local); text from local programs keeps non-ASCII characters.
- Dashboard: the proxy buttons respect "only when my own IP is used up"; used-up keys are skipped by Overview and Playground; controls no longer run off the edge on phones; the active-exit card shows only its own route's numbers.
- Linux: a fresh install over settings left by an uninstall keeps the old settings file beside the new one;
polygate passwordrefuses up front when the password is set byPOLYGATE_ADMIN_PASSWORD; the manager and the gateway agree on whether HTTPS is in use.
Upgrading
Windows: in 0.4.2 or later, open Settings → Updates → Update & restart. Otherwise download Polygate-0.5.6-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.