DevSpace
DevSpace is a self-hosted MCP server that connects ChatGPT or another MCP-capable host to approved local project folders so the host can inspect files, edit code, run commands, and work through a Codex-style coding loop.
DevSpace is useful because it turns the agent-harness question into a concrete connector: the model can stay in a chat host while the coding tools, files, terminal, project instructions, skills, and worktrees stay on the user's machine.
The Waishnav/devspace README describes DevSpace as a self-hosted MCP server for local coding projects. The setup guide documents Node, npm, Git, Bash, approved project roots, a local port, a public HTTPS tunnel, and an Owner password. The ChatGPT coding workflow guide documents workspace opening, checkout and worktree modes, project instruction files, skill discovery, tool naming, widgets, and shell usage. The security model says to treat DevSpace as remote access to the development machine and to keep filesystem roots, Owner password, tunnel controls, and shell access tightly scoped.
- Connect ChatGPT or another MCP host to selected local project folders.
- Let a chat-hosted model inspect code, edit files, run tests, and review diffs through explicit tools.
- Use managed worktrees for isolated coding sessions.
- Study how MCP connectors turn local development environments into agent harnesses.
DevSpace runs on the user's machine and exposes an MCP endpoint for a coding host. During setup, the user chooses which project roots are allowed, chooses or accepts a local port, enters a public HTTPS base URL from a tunnel or reverse proxy, and approves the client with an Owner password.
- Local server: the default local MCP endpoint is under `127.0.0.1:7676`.
- Remote access path: most users connect through a public HTTPS tunnel ending in `/mcp`.
- Scope control: DevSpace opens only configured workspace roots through its file tools.
Once a workspace is opened, DevSpace gives the connected host coding tools for a normal agent loop: inspect the repository, follow project instructions, make scoped edits, run verification commands, and show what changed.
- Workspace tools: read, write, edit, search through shell tools, and inspect directories.
- Execution tools: run shell commands for tests, builds, git, package scripts, and environment checks.
- Workflow tools: checkout mode, managed Git worktrees, `AGENTS.md` and `CLAUDE.md` discovery, skills, and optional tool-card widgets.
DevSpace should be evaluated as local-machine access, not as a harmless chat add-on. Its security docs recommend narrow filesystem allowlists, private Owner password handling, Host header allowlists, and additional tunnel protection such as Cloudflare Access or Tailscale identity controls. Shell commands run with the local user account, so the MCP client must be trusted.
DevSpace is not a language model, not Codex itself, and not an official quota or subscription product. The official sources support a local-workspace MCP connector story. Any claim about doubled Codex limits, model availability, or plan-specific quota behavior should be treated as community launch framing unless an official provider source confirms it.
DevSpace is a concrete harness connector around files, shell access, project instructions, skills, and worktrees.
DevSpace can expose skills, shell commands, and local files, so review and permission scoping matter.
DevSpace can support repeated coding loops where planning, execution, verification, and review stay connected.
Another productized coding-agent harness, focused on parallel CLI agents and worktree review.
Agent-ready backend infrastructure that also exposes powerful MCP and CLI surfaces to coding agents.
A coding-agent product often compared with Codex-style local development workflows.
DevSpace FAQ
Page-level questions for DevSpace.
Is DevSpace a coding agent?+
DevSpace is better understood as an MCP connector or harness server, not the coding agent itself. It gives a connected host tools for files, edits, shell commands, worktrees, project instructions, and skills, while the model and chat interface come from the MCP client.
Does DevSpace officially double Codex limits?+
No official DevSpace source used here defines it as a quota or limit-doubling product. The official documentation describes a self-hosted MCP server for local coding workspaces, so readers should evaluate it as a connector and verify any plan, model, or quota behavior with the relevant provider.
What should I secure before using DevSpace?+
Start with narrow allowed roots, keep the Owner password private, trust the connected MCP client, protect the public tunnel, and remember that shell commands run as the local user. Worktrees can isolate workflow changes, but DevSpace says they are not a security boundary.
Does DevSpace require exposing my local machine to the internet?+
Most normal ChatGPT-style use requires a public HTTPS tunnel or reverse proxy that forwards to the local DevSpace server. DevSpace does not create the tunnel itself; users provide Cloudflare Tunnel, ngrok, Pinggy, Tailscale Funnel, or another controlled HTTPS route.