nams:workspace

To switch the Codex session to a specific Neo4j workspace, you provide a structured JSON workspace selector to the NAMS plugin, which routes the command through its bundled CLI or fallback executable to update the active memory context.

NAMS workspace ambiguity occurs when multiple possible memory contexts exist for a Codex session without explicit selection, blocking the workflow until you resolve it by passing the correct workspace identifier to the plugin.

You pass the workspace selector to the Neo4j Agent Memory Service by issuing a request with the full workspace name or ID, which the Skill translates into structured JSON for safe CLI command execution.

Yes, you can use the NAMS workspace Skill with an installed fallback executable, as the command execution logic routes through the bundled plugin CLI first and automatically falls back to the installed executable if needed.

Yes, Neo4j workspace selection preserves the full workspace selector text provided in the initial request, ensuring the plugin accurately interprets and applies the exact target memory context without truncation.

You should manually target a NAMS workspace when you see multiple possible workspaces during a Codex session and need to ensure the agent continues in the specific memory context you intended without guesswork.