Toolport shows which skills and rules each coding agent loads
Toolport 2.2 adds a shared view of the skills and rules loaded by different coding agents. Users can inspect per-agent activation, find broken links or duplicate names and apply confirmed configuration fixes. Multiple Claude Code profiles have separate columns. The project’s own release document also warns that users on the 1.24.x line must install the new major version manually.
Artificial Intelligence··Midday
Loaded configuration becomes visible
Toolport 2.2.0 adds a Skills page displaying the skills and rules files loaded by installed coding agents. Among the supported clients are Cursor and Claude Code, alongside Codex. Gemini CLI, Hermes, Grok, OpenCode and Copilot CLI also appear in the view. It shows activation separately for each agent and the route to its rules file. Multiple Claude Code profiles receive individual columns. The project’s own release document supplies the description of these configuration functions.[1]
Configuration problems have repair controls
A review tab gathers broken links, duplicate skill names, shortened descriptions, unreadable rules files and skills still active in another location. After confirming a problem, users can make the suggested repair. They can also dismiss it. They can choose which application opens a file and send a skill they own to the trash. Skill activation switches use each agent’s native settings in ten supported agents. These are configuration controls, with no measured development-time saving supplied in the accepted account.[1]
The major-version move remains manual
Users on the 1.24.x release line do not receive 2.x automatically and are directed to migration guidance for manual installation. Auggie CLI and Tabnine are added as supported clients. Importing Auggie configuration preserves unrelated settings, while Tabnine remote connections retain authentication headers. A registry-lock fix addresses failures when multiple clients start together. Other corrections cover keyboard navigation and a clean gateway exit during slow Windows PowerShell updates.[1]