ns-switch-org

Name: ns-switch-org
Availability: InStock
Author: NodeSource

Switches the NodeSource organization used by nsolid-plugin across all installed harnesses.

6|7|Updated Jun 4, 2026

Search Tags:#authentication #oauth #cli #mcp #organization switching #nsolid #nodesource

Ready to run

npx skills add https://github.com/nodesource/nsolid-plugin --skill ns-switch-org-nodesource

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ns-switch-org
Source: https://github.com/nodesource/nsolid-plugin/tree/main/skills/ns-switch-org
Command: npx skills add https://github.com/nodesource/nsolid-plugin --skill ns-switch-org-nodesource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a NodeSource account belongs to multiple organizations, MCP data may come from the wrong org, and there is no way to keep two orgs active at once. This Skill guides the AI through safely re-authenticating against a different NodeSource organization. ## Core Features & Use Cases - Shared-credential warning: Explains that switching orgs changes the single NodeSource login shared by every installed harness (Claude Code, Codex CLI, OpenCode, Antigravity, Pi) and all three MCP servers. - Harness detection: Determines which harness is running so the correct `--harness` flag is passed to the CLI. - OAuth switch execution: Runs `npx -y [email protected] switch-org --harness <harness>` with an extended timeout, then relays the CLI's own output and follow-up guidance. - Use Case: A user notices N|Solid console data showing the wrong organization; the Skill warns about the global impact, triggers the browser sign-in with org picker, and reports the newly active org. ## Quick Start Switch my nsolid-plugin authentication to a different NodeSource organization for the Claude harness.

Frequently Asked Questions about ns-switch-org

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I switch NodeSource organizations in nsolid-plugin?▼

Run `npx -y [email protected] switch-org --harness <harness>` with your harness name (claude, codex, opencode, antigravity, or pi). A browser window opens for sign-in, and NodeSource shows an org picker automatically when your account belongs to multiple organizations.

Why is my N|Solid MCP data showing the wrong organization?▼

nsolid-plugin stores one set of NodeSource credentials shared by every installed harness and all three MCP servers. If you belong to multiple orgs, the active login may point to the wrong one, and switching orgs resolves it.

Does switching NodeSource orgs affect other installed harnesses?▼

Yes. Switching changes the single shared NodeSource login used by every harness where nsolid-plugin is installed, including Claude Code, Codex CLI, OpenCode, Antigravity, and Pi. Two orgs cannot be active at the same time.

What should I do if the switch-org OAuth flow fails?▼

Surface the command's error output directly to the user. Do not attempt workarounds such as manually editing ~/.agents/.nodesource-auth.json, since hand-editing the credential file is not supported.

How long does the nsolid-plugin switch-org command take?▼

The CLI's OAuth wait window is 5 minutes, so the command should be run with an extended timeout of at least 300000ms. The browser sign-in and org selection happen interactively during that window.