Local MCP
Your coding agent stays on your machine (Codex, Claude Code, Cursor,
VS Code) and drives Nullspace through MCP tools.
Agent workspaces
The coding agent itself runs inside a machine — isolated filesystem,
package installs, terminal, git, optional desktop.
Functions
Your agent project becomes a named, versioned job or service that your
backend can call repeatedly.
Framework integrations
Nullspace as a tool inside your app (OpenAI Agents SDK, LangChain) — or
your framework app deployed onto Nullspace (Claude Agent SDK, LangGraph,
CrewAI).
Which path fits?
| You want to… | Use | Tradeoff to know |
|---|---|---|
| Let a local coding agent create machines, run commands, and fetch files | Local MCP | The agent stays on your machine; only the work it launches runs isolated. |
| Put the coding agent itself in an isolated Linux workspace | Codex, Claude Code, Amp, or OpenCode | Provider credentials enter the machine environment. |
| Operate a repeatable agent app with runs, logs, outputs, and cleanup | Functions | Your backend owns product state and calls a named job or service. |
| Expose machine operations as one tool in a larger agent app | OpenAI Agents SDK, LangChain, or bring your own | Your app owns retries, tool schemas, and framework state. |
| Run a framework app as the managed process itself | Claude Agent SDK, LangGraph, or CrewAI | Nullspace owns runs and machines; the framework owns sessions and checkpoints. |
| Give an agent a browser or GUI | Desktop environments | — |
| Let a human inspect the same machine | PTY, SSH, or retained machines | — |
- Functions are jobs or services. A job is finite work with outputs. A service is a long-running HTTP process with URL, logs, and backing machine access.
- Nullspace run IDs are not conversation sessions. Framework session, thread, checkpoint, and flow state stays app-owned. Use volumes, retained machines, hibernate/auto-resume, or an external database when state must outlive one machine process.
The object model
Whichever path you pick, the same technical components apply:| Primitive | What it means |
|---|---|
| Machine | The isolated VM: commands, files, networking, PTY, SSH, desktop, volumes. |
| Agent project | A local directory with your app, a function.py definition, and an entrypoint. |
| Function | A named, uploaded project runnable as a job or service. |
| Run / service instance | One concrete execution, with logs, status, outputs, and a backing machine. |
| Framework state | Sessions, threads, checkpoints, memory — owned by your app, not Nullspace. |
Start with an example
Minimal job
Deploy and run a small project end to end.
HTTP service
A long-running Function service with a public URL.
Workspace checks
Clone a repo in a machine and run checks like an agent.