Skip to main content
Use the Nullspace skill when local coding agents should understand the Nullspace SDK, CLI, MCP server, machine primitives, and agent templates. The installed references include a warm-pool recipe for agents that need to prepare a custom template pool, wait for ready capacity, create machines with prefer or require, then drain the pool after a burst.

​
Install From GitHub

Restart the coding agent if the skill does not appear immediately.

​
Install From A Checkout

Codex repo-local:
Codex user-local:
Claude Code project-local:
Claude Code user-local:

​
Always-On Project Context

Copy skills/nullspace/assets/project-AGENTS.md or skills/nullspace/assets/project-CLAUDE.md into a project when Nullspace should be persistent context, not only an invoked skill. Keep root project instructions short. Broad orientation belongs there; workflow details belong in the skill and its references.

​
MCP

Install the SDK with CLI and MCP extras:
For Claude Code and Codex on a local laptop, install the project-local docs and MCP config pack after the SDK install:
Use --agent claude-code or --agent codex when you only want one local agent surface. The command writes .nullspace/agent-docs/ and project-local agent instructions. For Claude Code it installs .claude/skills/nullspace; for Codex it installs .agents/skills/nullspace. It does not require an API key and does not edit user-level config files. If you are installing from the repository skill files manually instead of using nullspace docs install, copy:
For Codex manual setup, add the TOML block from skills/nullspace/assets/codex-config.toml to ~/.codex/config.toml. Start the coding agent from a shell where these are set:
For platform-specific setup and verification in Codex, Claude Code, Cursor, and VS Code, see the Local MCP guide.

​
Check Local Setup

From the installed skill directory:
For offline schema checks without hosted API validation:
The script does not print API key values.