nams:workspace

Select the NAMS workspace for Codex sessions via plugin or nams-hooks CLI.

Updated May 10, 2026
One-click install
npx skills add https://github.com/kubamarchwicki/nams-plugins --skill nams-workspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nams:workspace
Source: https://github.com/kubamarchwicki/nams-plugins/tree/main/templates/codex/plugins/codex-nams-hooks/skills/workspace
Command: npx skills add https://github.com/kubamarchwicki/nams-plugins --skill nams-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicitly select the NAMS workspace for a Codex session when multiple workspaces exist or ambiguity is reported, ensuring the correct context is used for memory and command routing.

Core Features & Use Cases

  • Enable explicit workspace selection via a simple command so the chosen workspace is used for the current Codex session.
  • Detect the plugin root (the ancestor directory containing .codex-plugin/plugin.json) to route the workspace command through the bundled CLI; if the root is not discoverable, fall back to the standalone nams-hooks CLI.
  • Improve reliability in multi-workspace environments by providing a safe, predictable workflow with clear fallbacks and minimal friction for developers integrating Codex plugins.

Quick Start

Invoke the command with the explicit selector to set the workspace for the current Codex session.

Frequently Asked Questions about nams:workspace

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

FAQPage Schema
How do I select a specific workspace for a Codex session when multiple workspaces exist?

To select a Codex workspace, you invoke the explicit workspace selector command, which sets the correct context for memory and command routing during your current session.

What does workspace selection do for Codex memory service routing?

Workspace selection ensures the correct context is used for memory and command routing in Codex sessions, preventing ambiguity when multiple workspaces are available.

How does the plugin CLI find the correct workspace root for Codex?

The plugin CLI detects the ancestor directory containing the .codex-plugin/plugin.json file to route the workspace command through the bundled CLI.

What happens if the Codex plugin root directory is not discoverable?

If the plugin root is not discoverable, the workspace command falls back to using the standalone nams-hooks CLI to execute the selection.

Can I use this workspace selection approach in multi-workspace Codex environments?

Yes, this approach is designed for multi-workspace Codex environments, providing a safe, predictable workflow with clear fallbacks for developers integrating Codex plugins.