Skip to content

Releases

v0.11.3

Choose a tag to compare

@github-actions github-actions released this 28 Oct 23:26
Immutable release. Only release title and notes can be modified.
  • Dialogs: Escape closes the "Discard changes?" prompt and leaves Settings open (the same for the config editor); before, it opened the prompt again. In Chrome and other Chromium browsers, pressing Escape again without a click no longer hides a dialog the dashboard still showed as open, which left the page unresponsive.
  • Settings: in the macOS app, Appearance shows the app icon chosen in the menu bar app's menu, also when it changed while the dashboard was open.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.11.3.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.11.2

Choose a tag to compare

@github-actions github-actions released this 27 Oct 23:25
Immutable release. Only release title and notes can be modified.
  • Settings, reorganized: a larger window whose sections fit without scrolling in the app's window, each a few groups of rows (label and explanation on the left, control on the right): General (startup, projects folder, editor, terminal, language), Appearance (mode, a one-row palette, layout and, in the macOS app, the app icon), Servers, Events, Environment, Coding agents and Advanced. Save stays in the footer on every section and says when there are unsaved changes, and closing with unsaved changes asks first.
  • Settings, new: the dashboard's port can be set (empty lets the daemon choose; it applies after a daemon restart), and Advanced has the config file (edit it in the dashboard or open it in your editor), the server logs folder and Computers (Settings and the server form).

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.11.2.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.11.1

Choose a tag to compare

@github-actions github-actions released this 27 Oct 21:00
Immutable release. Only release title and notes can be modified.
  • Every setting in the dashboard: Settings has sections (General, Servers, Environment, Events, Docker, Coding agents) that edit the config file's top-level keys, from the projects folder, restore and notify to path, env, login_env, umask, the hook commands and docker_start, with one Save, the daemon's errors, defaults as placeholders and the daemon's version in the footer. Only port stays in the file. A server's form has It's a task (runs once) and an Advanced section with every other server key: ready_log, ready_after, stop_timeout, retry_after, memory_limit, enabled, schedule, watch, the hook commands, unready_after, wrap, umask, lan, open, icon and projects. Saves change only the keys you edited and keep your comments; a value set back to its default is removed (Settings and the server form).
  • Settings: the dashboard's Settings has Startup with Start Portside at login in the macOS app (in a browser, the portside service install command), so the setting is no longer only in the menu bar app's menu and on the getting-started page.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.11.1.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.11.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 19:59
Immutable release. Only release title and notes can be modified.
  • Crashed servers start again by default. A server without a restart setting now uses on-failure: after a crash it starts again with backoff (1, 2, 4, 8 and 16 s), and only after 5 restarts in a row does it stay crashed and get reported. Tasks (oneshot = true) still default to no, so a failed migration is reported at once rather than repeated. To keep the old behavior for a server, set restart = "no"; the dashboard's form now writes that choice explicitly.
  • Getting started: in the macOS app, the dashboard's getting-started page offers Start Portside at login, on until you have chosen once (there or in the app's menu) and applied when you find projects or add a server, so your servers come back after a restart. In a browser it shows portside service install instead.
  • Settings shortcut: ⌘, (Ctrl+, outside macOS) opens Settings in the dashboard, and the app menu has Settings… with ⌘,.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.11.0.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.10.2

Choose a tag to compare

@github-actions github-actions released this 27 Oct 17:09
Immutable release. Only release title and notes can be modified.
  • Fixed, tasks: portside restart of a task (alone, with other servers, from the dashboard or restart_server) runs it again instead of leaving it stopped. After an upgrade in place, a server that was waiting for a task whose process ended during the upgrade fails with the task's note instead of running the task a second time.
  • Fixed: a server whose process exits while the daemon upgrades in place continues its round of automatic restarts instead of starting a new one, so on_crash reports it after the same number of restarts as without the upgrade. A start no longer races with a config reload over the server's dependencies.
  • Fixed, dashboard: saving a server's form refuses with a conflict when the config file was changed at the same moment from the CLI or an editor, instead of overwriting that change.
  • Fixed, MCP: with --dir, list_ports no longer shows another program that took the port of a stopped server in scope.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.10.2.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.10.1

Choose a tag to compare

@github-actions github-actions released this 27 Oct 14:21
Immutable release. Only release title and notes can be modified.
  • watch: a server with many watched files is scanned less often instead of costing more, about 2 % of one core at most for all servers together, and a large tree slows only its own server; a change among 20,000 files takes a few seconds to notice (Periodic checks). ** also skips venv.
  • portside check counts a task as healthy while its process runs (not while it waits for its dependencies), so a long scheduled task no longer fails a monitor's check; a task you name must still be done.
  • Fixed: a stop asked for while the daemon upgrades in place (about a second) is refused with a message to try again, instead of being lost or counted as a crash by the new daemon. Two servers that need the same task, started at once, no longer run it twice.
  • Fixed, tasks: servers started together share a task's run also when it fails, instead of running it again; a task started as a dependency gets a fresh round of automatic restarts; a watch restart of a task or server no longer fails the servers and ensure calls waiting for it.
  • Fixed, schedules: rare dates such as a Sunday 29 February are found (the next run is searched across 400 years, not 10), and the dashboard names the right day for a run just after a clock change.
  • Menu bar app: counts servers only, as the dashboard does, so a running task no longer keeps the icon amber as a server still starting.
  • Security docs: a server with watch runs whatever is saved in its watched files, whatever an agent's MCP mode or --dir scope (Security).

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.10.1.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.10.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 12:24
Immutable release. Only release title and notes can be modified.
  • Tasks: oneshot = true makes an entry a task that runs to completion, such as a migration. Servers that depends_on it start once it exits with code 0, and are crashed with a note such as dependency migrate failed: exited with code 1 when it fails. ensure, up --wait and ensure_server run the task again and wait for its end; servers started together share one run. A task has no port, shows as done after a successful run, and counts for portside check only while it runs, when it failed, or when you name it (Tasks).
  • Schedules: schedule = "30 2 * * *" starts a task or server at the times a crontab expression matches, in local time (five fields, names, ranges, lists, steps and @daily style macros). A run missed during sleep or while the daemon was down happens once afterwards, a server still running skips the run, PORTSIDE_TRIGGER is schedule, and enabled = false pauses it. portside status, the dashboard and list_servers show the next run (Schedules).
  • memory_limit (top level or per server, such as "2GB"; "0" turns an inherited one off) stops a server whose processes use more memory, checked with each usage sample (every 30 seconds, every 2 seconds while the dashboard shows usage). It counts as a crash with a note such as used 2.3 GB, over memory_limit 2 GB: the restart policy applies and on_crash gets the note. Worktree copies have their server's limit; containers are not covered (Memory limit).
  • watch = ["src/**/*.py", "pyproject.toml"] restarts a server once changes to the files it matches, relative to its dir, have stopped for about a second, and starts a crashed one again after a change, so fixing the error brings it back. The log names the change (restarting: changed src/app.py (+3 more)) and PORTSIDE_TRIGGER is watch. A server you stopped ignores changes, and a task restarts only while it runs. Files are polled every second, only in directories a pattern can match, skipping .git, node_modules and similar folders unless a pattern names them. The dashboard marks such a server watching (Restart on file changes).
  • Hook commands: PORTSIDE_TIME gives when the event happened (RFC 3339), so a monitor can order reports whose commands finished out of order.
  • Fixed: an automatic restart still waiting for its backoff when the daemon upgraded in place was lost with restore = false, or happened at once with a fresh count of restarts; it now happens at its time in the new daemon and continues the count, unless the config the new daemon loads sets restart = "no".
  • Fixed: a server that was still starting when the daemon upgraded in place no longer stays down with restore = false, nor when the upgrade fails: the start goes on.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.10.0.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 10:20
Immutable release. Only release title and notes can be modified.
  • Hook commands: on_unready runs when a running server has not answered on its port or health path for unready_after (a minute unless set), and on_recover when a server that on_crash or on_unready reported is ready again, with PORTSIDE_RECOVERED_FROM and PORTSIDE_DOWNTIME. Like on_crash, both are set at the top level or per server, and one script can tell the events apart by PORTSIDE_EVENT.
  • Crash command: PORTSIDE_STREAK counts the crashes for good in a row without the server being ready in between, so a monitor that starts failed servers again can report each problem once, and PORTSIDE_TRIGGER says what began the run (start or restore). The streak and an open problem survive daemon restarts and upgrades.
  • umask (top level or per server) sets the mode mask for the files a server creates, such as "0007"; without it servers keep the daemon's, which launchd and systemd set to 0022, readable by other accounts.
  • login_env = false gives servers the daemon's own environment plus path and env instead of the login shell's, for servers whose environment the config alone should decide. portside doctor says which one servers get.
  • retry_after (top level or per server, for restart = "on-failure" or "always") starts a server again that long after its automatic restarts gave up or its start failed, with another 5 restarts, until it runs or you stop it; PORTSIDE_TRIGGER is then retry. The dashboard offers Stop while it waits, and the menu bar app still announces the crash.
  • Docs: the Linux server guide explains that systemctl --user restart portside stops every server, while portside daemon restart keeps them running.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.9.0.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 07:36
Immutable release. Only release title and notes can be modified.
  • MCP --dir scope: a container counts as a scoped server's only through the server's projects in the config or a Compose working directory inside the scope, so a project's supabase/config.toml naming another project's ID no longer exposes that project's containers; a Supabase CLI project ID listed in a server's projects belongs to that server alone, also on the dashboard. Containers and list_ports no longer name a server outside the scope, and ensure_server refuses a dir outside it.
  • Worktree copies: dir must be a worktree git has registered for the repository; a directory whose .git file only points into the repository is refused.
  • MCP: program output quoted by ensure_server and restart_server errors and by container_action is marked as untrusted. The docs say plainly that start and full modes run code the agent can edit.
  • Security, sharing: unpairing a device, or pairing it again, now also refuses its request whose body was still arriving and ends every connection of the old pairing; the body of a paired device's request must arrive within 30 seconds. On Linux the sharing listener accepts connections only from root or your own account, which tailscaled runs as, so other local accounts that read the Serve path cannot send it forged Tailscale headers.
  • Security, sharing: a reply relayed from the connected computer is cut off at 64 MiB, since the daemon may hold a whole reply to sign it for the CLI, so a computer that was taken over cannot exhaust this one's memory.
  • Security, sharing: this daemon never follows a redirect from the connected computer, cuts off a relayed reply that stops for a minute, ignores a state that is not a JSON object, and opens that computer's server addresses only on this computer, at the forwarded port or through the proxy, whatever host they name; the dashboard ignores a state of another shape than it reads.
  • Security: the CLI and the macOS app never follow a redirect from what answers on the daemon's port, for requests and WebSockets alike, which could have sent a signed request elsewhere before its reply was checked; writes need an Origin that is a plain origin (no user, path or query).
  • CLI and MCP: names, notes and commands are printed with control characters replaced in tables, and the list tools tell agents that these fields are data, not instructions.
  • Security, pairing: portside pair <computer> reads the code from standard input (it asks on a terminal, or reads a pipe); the code as an argument, which other accounts could read and redeem first, is refused.
  • Security, forwarded ports: forwarded ports hold at most a quarter of the daemon's open-file limit (about 11,000 ports on a Mac, all of them on Linux), servers first; ports beyond it are listed as over the limit in the Computers window, portside computers and portside doctor, and turning a port off makes room. Binding forwarded ports and checking them for local listeners happen outside the lock other requests wait for, at most 128 every 2 seconds, so thousands of ports no longer stall the dashboard; a local server starting on a port that is being bound gets it, and the dropped bind never forwards a connection. This computer never listens for a forwarded port on the daemon's own, default or fallback ports; such a remote port is listed as busy and can go to another local port.
  • Fixed: starting a server while it is still stopping (portside down and then ensure, or ensure_server and depends_on meanwhile) starts it again once its whole process group has exited, so a child still holding the port does not block it, also when the server exits just as the start arrives or is renamed meanwhile, instead of leaving it stopped until ensure timed out.
  • Fixed: a daemon start after a stop no longer ends a process group whose id another program got in the meantime: a stopping daemon removes its servers' groups from the state once they have exited, and after a crash a leftover group is ended only when its processes can be tied to the server.
  • Fixed: an upgrade in place is refused until a stopping server's processes have all exited, also after its main process did, so the upgrade no longer cuts the stop short and leaves a child running.
  • Fixed: a server that exits while the daemon upgrades in place counts as crashed, so its restart policy or on_crash applies, instead of counting as stopped; with restart = "no" it stays down also when restore brings back the other servers.
  • Fixed: shutting the daemon down while a server stops no longer sends it a second Ctrl-C, which made docker compose abort its graceful stop, and waits until that stop has ended every process the server started, also for a server removed from the config meanwhile; a second portside down also waits for it, and no restart stays announced for a server that crashed just before.
  • Fixed: an on_crash command that leaves a background process holding its output no longer runs forever and takes one of the four slots.
  • Fixed: ready_log and plain logs strip color sequences with : parameters, such as \x1b[4:3m (curly underline), so an anchored ready_log matches.
  • Fixed: a state file that cannot be written (for example a read-only state directory) is reported in the daemon log and as a warning in the dashboard and portside doctor, instead of silently losing which servers you stopped.
  • portside daemon info includes configError also when a running daemon goes on with the last config that loaded.
  • Fixed: turning a server on or off in the config keeps a comment on the enabled line, edits keep the blank lines that end the file, a key written in another case (Enabled) is edited in place, and a server table with two keys that differ only in case (cmd and Cmd) is refused instead of loading either.
  • Linux is a first-class platform (x86-64, arm64), next to macOS: CI runs the systemd user service end to end and an upgrade from the latest release on every change, and the README installs it with the same Homebrew tap (brew install --formula padmk/tap/portside) or from the release archives.

Install

With Homebrew on macOS 26 or later (Apple Silicon), the app and the command:

brew install --cask padmk/tap/portside

On macOS or Linux (x86-64, arm64), the command and dashboard, built from source:

brew install --formula padmk/tap/portside

Portside-0.8.0.zip below is the same app, and the portside_*.tar.gz archives hold the command alone. See the README for details.

v0.7.2

Choose a tag to compare

@github-actions github-actions released this 26 Oct 19:17
Immutable release. Only release title and notes can be modified.
  • Dashboard, menu bar and CLI: a running server that stopped answering on its port or health path shows as not responding (an amber diamond in the dashboard, an orange light in the menu bar, a yellow dot in portside status) and is counted apart from the running ones, as portside check already reported it.
  • Upgrades in place: the upgrade is refused, and the servers keep running under the current daemon, when the terminal of a server still waiting for its ready_log line cannot be paused, so that line cannot slip between the two daemons; for other servers it is only logged.
  • CI: the Linux service run also upgrades the daemon while a server is still waiting for its ready_log line, and both Linux and macOS upgrade the latest published release in place to the new build (scripts/upgrade-from-release.sh).

Install

macOS 26 or later on Apple Silicon:

brew install --cask padmk/tap/portside

Portside-0.7.2.zip below is the same app. The portside_*.tar.gz archives hold the command-line binary alone (Linux is a preview). See the README for details.