v1.7.2
Toolport v1.7.2
Joining a Toolport Team no longer freezes the app.
Two separate bugs locked things up when you connected the desktop app to a team. Both are
fixed.
The app no longer hangs on join. The team network calls (join, background config sync, admin
push) ran on the app's UI thread, and the sync holds a roughly 30-second long-poll open, so
simply being connected to a team blocked the interface and the window went "Not Responding."
They now run off the main thread.
Joining no longer exhausts memory. The background sync rewrote the local registry on a timer,
and every gateway re-spawned each server on the change, leaking processes until RAM ran out.
Saves are now a no-op when nothing changed, and the gateway only rebuilds when the server set
actually changes.
Alongside the Teams work:
- Review bulk imports before applying. Detect or paste a batch of servers and confirm the
full set before it lands, with scoped package names preserved and no stale-row or same-name
collisions. - Tighter spawn screening. Destructive-command screening now catches PowerShell
-EncodedCommandandPERL5OPT. - Project-root working directory. A
${ROOT}server runs in the client's actual project
root, resolved live from its MCP roots.
Upgrade
- In-app: click Toolport v1.x.x in the sidebar footer (shows Update to v… when a
release is available). - Installer: Releases.
Contributors
First-time community contributors, thank you:
- @glasses-and-hat, unit tests for the token-savings formatter (#277)
- @SK-Sathyavada-008, a consolidated CONDUIT environment variable reference (#278)
Changelog: 1.7.2.