Skip to content

Toolport

v1.5.3 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 19d MCP Developer Tools
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai ai-agents anthropic claude cursor developer-tools
+10 more
gateway llm local-first mcp mcp-server model-context-protocol react rust tauri vscode

Summary

AI summary

Fixed org‑forced safety locks being permanently applied when leaving a team.

Full changelog

Teams reliability and activation batch, ahead of the Teams launch.

Fixed

  • Org-forced safety locks are released when you leave a team. A team that enforced human-in-the-loop approval, destructive-tool blocking, content defense, or quarantine-on-drift used to bake that setting permanently into your own settings, so leaving the team left the lock stuck on with no way to turn it back off. These org forces are now tracked separately from your own settings and cleared the moment you leave; your own toggles are never touched. (#209)

Added

  • "Joining a team?" onboarding path. The first-run wizard now offers first-class invite-code entry, so a team member who was told to install Toolport can join their team immediately instead of clicking through solo setup to look for it. (#210)
  • Near-instant team policy sync. Members now long-poll the team config, so an admin's policy or access change in the dashboard enforces on member machines in about a second instead of at the next poll interval. Falls back cleanly against an older team server. (#211)

Full Changelog: https://github.com/tsouth89/toolport/compare/v1.5.2...v1.5.3

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Toolport

Get notified when new releases ship.

Sign up free

About Toolport

All releases →

Beta — feedback welcome: [email protected]