STYGION Panel a0.3.1

What 0.3.0 shipped, and what running it for an evening turned up.

Console commands actually arrive

You could type into the console and the server would not move. The cause was not the sending — it was what had happened earlier.

Closing a podman attach sends the container end-of-input. The panel opened one attach per console viewer and killed it when the page closed, which closed the write end of the pipe the server reads. A Minecraft server does not exit on that; it simply stops reading commands for as long as it runs. So the first person to open a console was also the last person able to type in it, and everybody after that was writing into a stream nothing was reading.

Worse, the graceful stop used the same path — so shutting a server down with its own stop command poisoned its console too.

A container's input is now opened once and held for as long as the container runs. Viewers come and go against it; closing a console closes only the log stream that person was reading.

After updating, restart your servers once. A container that is already running has its input closed for good; the fix applies to the next start.

The panel can replace its own binary

update failed: permission denied on the first press of Update. The binary sat in a directory owned by root, and a self-update has to write next to the running binary to swap it atomically. It lives in /opt/<instance>/ now, owned by the user the panel runs as, with a symlink left in /usr/local/bin. Existing installs need the directory handed over once:

sudo chown -R stygion:stygion /opt/stygion

The error says all of this now, instead of naming a temp file nobody chose.

MCP has a screen

The agent surface was running with nothing in the panel to show for it — the key was only readable in the env file. Admin → Application API now says whether it is on, what address an assistant connects to, and every tool it offers. The key is behind a second click and revealing it is written to the activity log.

Subscription moved to the admin workspace

It was in user Settings, while its API was admin-only — so an ordinary user was shown a card that could only fail. It is Admin → Subscription now, beside Updates. Billing stays where it was: that is you selling servers to your customers, this is you buying the panel from us.

Updating shows what it is doing

A real dialog now, from the confirmation through downloading, verifying the checksum and restarting, to "version X is running". It holds until it is finished. No percentage bar — the update is one server-side call, so there are no honest percentages to show.

The team does not pay

An account on the STYGION team gets the panel for as long as it is on the team, with nothing to buy and no date to renew. It reads the same flag the rest of the site does, so joining and leaving both take care of themselves.