Skip to content
Back to search

devspace

SkillWorks with Claude CodeGitHub

Minimal Coding Agent Harness on MCP for ChatGPT, Claude, Hermes, Grok Bot, OpenClaw

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/waishnav--devspace/badge.svg)](/listings/waishnav--devspace)

HTML

<a href="/listings/waishnav--devspace"><img src="/api/listings/waishnav--devspace/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

DevSpace requires Node `>=22.19 <27`.

Install the DevSpace CLI:

npm install -g @waishnav/devspace

Then initialize DevSpace:

devspace init

Or run it without a global install:

npx @waishnav/devspace init

During setup, DevSpace asks for:

- where you will use it: ChatGPT, Coding Agents, or both - which agents DevSpace may use as subagents

The first choice is where you invoke DevSpace from. The subagent choice is separate: ChatGPT or another coding agent can delegate work through DevSpace to the agents you select there.

If you select ChatGPT, setup also asks which local project folders it may open and for your public HTTPS base URL from Cloudflare Tunnel, ngrok, Pinggy, Tailscale Funnel, or another reverse proxy. A Coding Agents-only setup asks neither question: local commands use the current Git project, or the current directory outside a repository.

Use the public origin without `/mcp` during setup:

https://your-tunnel-host.example.com

You will configure your MCP client with the public `/mcp` URL after setup. Run `devspace serve` when using ChatGPT. For Coding Agents, setup prints a `skills` command and lets the Skills CLI handle installation.

When the client connects, DevSpace opens an Owner password approval page. Enter the Owner password printed by `devspace init`. It is also stored in:

~/.devspace/auth.json

Keep that password private.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 276 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <picture>
  3. <img src="https://raw.githubusercontent.com/Waishnav/devspace/main/.github/assets/devspace-logo.png" alt="DevSpace logo" width="140">
  4. </picture>
  5. </p>
  6. <h1 align="center">DevSpace</h1>
  7. <p align="center">Give ChatGPT, Claude, and Grok Bot your computer. Let any coding agent hand work to any other.</p>
  8. <p align="center">
  9. <a href="https://www.npmjs.com/package/@waishnav/devspace"><img alt="npm" src="https://img.shields.io/npm/v/%40waishnav%2Fdevspace?style=flat-square" /></a>
  10. <a href="https://github.com/Waishnav/devspace/actions/workflows/ci.yml"><img alt="CI" src="https://img.shields.io/github/actions/workflow/status/Waishnav/devspace/ci.yml?style=flat-square&branch=main" /></a>
  11. <a href="https://github.com/Waishnav/devspace/blob/main/LICENSE"><img alt="License" src="https://img.shields.io/npm/l/%40waishnav%2Fdevspace?style=flat-square" /></a>
  12. </p>
  13. ![DevSpace in ChatGPT: opening a workspace, fixing a bug, delegating a review to Codex, and reviewing the changes](https://raw.githubusercontent.com/Waishnav/devspace/main/website/public/media/devspace-in-chatgpt.gif)
  14. DevSpace is the agent-agnostic layer between the AI you talk to and the coding
  15. agents on your machine. It does two things:
  16. - **Connects MCP hosts to your machine.** ChatGPT, Claude, and proactive agents
  17. like Grok Bot, OpenClaw, and Hermes open a workspace, read and edit files, run
  18. your tests, and show you a review card of the diff — against your real
  19. checkout, through a tunnel you own.
  20. - **Lets agents delegate to each other.** Codex, Claude Code, OpenCode, Pi,
  21. Cursor, Copilot, and Grok Build run as subagents of whichever agent is in
  22. charge, using the CLIs and subscriptions you already have. Parallel writers
  23. get their own Git worktrees.
  24. Your agent stays the orchestrator: DevSpace never runs a hidden agent loop of
  25. its own. And there is no DevSpace service — everything runs locally with your
  26. credentials.
  27. ## Sponsors and Special Thanks
  28. <!--
  29. <table>
  30. <thead>
  31. <tr>
  32. <th>Sponsor</th>
  33. <th>About</th>
  34. </tr>
  35. </thead>
  36. <tbody>
  37. <tr>
  38. <td align="center" width="220">
  39. <a href="https://rebates.ai/">
  40. <img
  41. src="https://app.rebates.ai/brand/rebates-lockup.svg"
  42. alt="Rebates"
  43. width="170"
  44. >
  45. </a>
  46. </td>
  47. <td>
  48. <strong>The ads in your terminal pay you.</strong><br><br>
  49. <a href="https://rebates.ai/">Rebates</a> adds one optional
  50. sponsored footer to your coding agent and pays you cash back for every
  51. session in which it is shown. Turn it off at any time.
  52. </td>
  53. </tr>
  54. </tbody>
  55. </table>
  56. -->
  57. <p>
  58. DevSpace is open to new sponsors.
  59. <a href="https://x.com/wshxnv">Get in touch to become one.</a>
  60. </p>
  61. ## Installation
  62. macOS, Linux, and WSL:
  63. ```bash
  64. curl -fsSL https://devspace.run/install | sh
  65. ```
  66. Windows (DevSpace also needs Git Bash):
  67. ```powershell
  68. powershell -c "irm https://devspace.run/install.ps1 | iex"
  69. ```
  70. The installer uses a compatible Node (`>=22.19 <27`) on your `PATH` or
  71. downloads Node 24 LTS for DevSpace alone, installs without `sudo`, and starts
  72. `devspace init`. Rerun it to update. If you manage Node yourself,
  73. `npm install -g @waishnav/devspace` followed by `devspace init` also works.
  74. `devspace init` asks where you will use DevSpace and which agents it may run as
  75. subagents. Each question can also be answered with a flag, so scripts and
  76. agents can set it up without prompts:
  77. ```bash
  78. devspace init --yes # subagents only
  79. devspace init --public-url https://your-tunnel.example.com --roots ~/work # also serve an MCP host
  80. ```
  81. **Let your agent set itself up.** The **Copy prompt** button on
  82. [devspace.run](https://devspace.run) copies a prompt you can paste into Codex,
  83. Claude Code, or any agent with a shell. It installs, configures, and checks
  84. DevSpace without asking you anything.
  85. ## Use It from Your Coding Agents
  86. Subagents need no server, tunnel, or OAuth. Install the skill that teaches your
  87. agent the workflow, then delegate:
  88. ```bash
  89. devspace agents skill --install <claude-code|codex|opencode|agents>
  90. # Cursor: devspace agents skill --install cursor --project
  91. devspace agents run codex "Review the staged diff for correctness"
  92. devspace agents run pi "Check the staged diff for test gaps"
  93. devspace agents wait <id> <id>
  94. ```
  95. - **Profiles** turn your "which model for which job" choices into named roles
  96. (`planner`, `reviewer`, …) as Markdown files you own.
  97. - **Worktrees** (`--worktree`) let agents edit in parallel without touching
  98. your checkout.
  99. - **Dynamic workflows** (experimental, `DEVSPACE_EXPERIMENTAL_WORKFLOWS=1`) let
  100. the orchestrator write a small, resumable script with `agent()`,
  101. `parallel()`, `pipeline()`, and `phase()` instead of prompting step by step.
  102. ## Use It from ChatGPT, Claude, and Other MCP Hosts
  103. Start a tunnel (Cloudflare Tunnel, ngrok, Pinggy, Tailscale Funnel, or your
  104. own HTTPS reverse proxy) to `http://127.0.0.1:7676`, run `devspace serve`, and
  105. add the public `/mcp` URL as a connector in your host:
  106. ```text
  107. https://your-tunnel-host.example.com/mcp
  108. ```
  109. When the host connects, DevSpace opens an Owner password approval page. The
  110. password is stored in `~/.devspace/auth.json`; keep it private. The `/mcp`
  111. endpoint serves the 2026-07-28 protocol and older 2025-era clients without any
  112. configuration.
  113. Once connected, the host can open one of your allowed project folders as a
  114. workspace and:
  115. - read, write, and edit files, and search code
  116. - run shell commands for tests, builds, Git, and package scripts
  117. - use isolated Git worktrees for parallel sessions
  118. - follow project instructions from `AGENTS.md` and `CLAUDE.md`, and discover
  119. your skills
  120. - show a change-review card at the end of a turn
  121. - delegate to your coding agents through the same `devspace agents` CLI
  122. > [!NOTE]
  123. > Using DevSpace as an MCP connector isn't against OpenAI's Usage Policies — it's
  124. > a standard custom App/connector setup, and writing or running code isn't a
  125. > restricted use case. But your account is governed by your usage, not by
  126. > DevSpace. Don't point it at anything that would violate your provider's terms.
  127. > Used normally, you're fine. (Based on OpenAI's Usage Policies and Service Terms
  128. > as of June 2026.)
  129. ## Mental Model
  130. DevSpace is remote access to selected local folders, plus a way for your
  131. agents to work together.
  132. You decide which roots an MCP host may open. Inside a workspace the host has
  133. powerful local capabilities, including shell execution, so treat a connected
  134. host like a trusted coding partner with access to your machine. Subagents run
  135. with your local user's authority and logins, scoped to the project they are
  136. started from.
  137. ## Platform Support
  138. DevSpace supports Linux, macOS, and Windows environments with a Bash-compatible
  139. shell.
  140. | Platform | Status | Notes |
  141. | ------------------------------------------------- | ----------------- | ---------------------------------------------- |
  142. | Linux | Supported | Requires Node, npm, Git, and Bash. |
  143. | macOS | Supported | Requires Node, npm, Git, and Bash. |
  144. | Windows with Git Bash, WSL, MSYS2, or Cygwin Bash | Supported | Git Bash is the simplest native Windows setup. |
  145. | Windows PowerShell or `cmd.exe` only | Not supported yet | Install Git Bash or use WSL. |
  146. Run this to inspect your local setup:
  147. ```bash
  148. devspace doctor
  149. ```
  150. ## Documentation
  151. Full documentation lives at [devspace.run/docs](https://devspace.run/docs):
  152. - [Quickstart](https://devspace.run/docs/quickstart)
  153. - [Connect ChatGPT, Claude, Grok Bot, and other MCP hosts](https://devspace.run/docs/connect/mcp-hosts)
  154. - [Use DevSpace from Codex, Claude Code, Cursor, OpenCode, and bots](https://devspace.run/docs/connect/coding-agents)
  155. - [Subagents](https://devspace.run/docs/orchestration/subagents) and [agent profiles](https://devspace.run/docs/orchestration/profiles)
  156. - [Dynamic workflows](https://devspace.run/docs/orchestration/dynamic-workflows)
  157. - [CLI reference](https://devspace.run/docs/reference/cli) and [configuration reference](https://devspace.run/docs/reference/configuration)
  158. - [Security model](https://devspace.run/docs/concepts/security)
  159. - [Troubleshooting](https://devspace.run/docs/reference/troubleshooting)
  160. ## Philosophy
  161. Every piece of software is becoming conversational, and every provider is
  162. racing to make _their_ agent the orchestrator.
  163. In practice, people already pick a different model and harness per task: one
  164. to plan, another to implement, a cheap one to explore, a second vendor to
  165. review. That matrix is personal, and it changes every few weeks.
  166. DevSpace keeps it yours. Whichever agent you talk to — ChatGPT, Claude, Grok
  167. Bot, or a coding agent in your terminal — can reach your machine and hand work
  168. to the others, through explicit, inspectable tools instead of one vendor's
  169. closed loop.
  170. ## Built by Waishnav
  171. I'm Waishnav. I like building opinionated products and tools, and DevSpace is one example.
  172. This year, I began my journey to build a one-person, multi-agent company capable of generating millions in revenue. If you want to follow the failures, wins, lessons, and everything in between, come hang out with me on [X](https://x.com/wshxnv).
  173. ## More from me
  174. <table>
  175. <thead>
  176. <tr>
  177. <th>Project</th>
  178. <th>About</th>
  179. </tr>
  180. </thead>
  181. <tbody>
  182. <tr>
  183. <td align="center" width="220">
  184. <a href="https://gitcms.dev/">
  185. <img
  186. src="https://gitcms.dev/brand/gitcms-logo.svg"
  187. alt="GitCMS"
  188. width="48"
  189. /><br />
  190. <strong>GitCMS</strong>
  191. </a>
  192. </td>
  193. <td>
  194. <strong>The CMS for code-first and AI-built websites.</strong><br><br>
  195. GitCMS gives your team, your clients, and AI agents one safe place to
  196. edit, review, and publish website changes, while everything stays in
  197. your site’s repository. No migration and no content database.
  198. <a href="https://gitcms.dev/">Learn more</a>.
  199. </td>
  200. </tr>
  201. </tbody>
  202. </table>
  203. ## Local Development
  204. For working on DevSpace itself:
  205. Install pnpm 11.25.0, the version pinned in `package.json`, with
  206. `npm install --global pnpm@11.25.0`, then:
  207. ```bash
  208. pnpm install --frozen-lockfile
  209. pnpm dev:seed
  210. pnpm dev
  211. pnpm typecheck
  212. pnpm test
  213. pnpm build
  214. pnpm start
  215. ```
  216. `dev:seed` forks your normal DevSpace config and SQLite state into an ignored
  217. checkout-local `.devspace-dev/` directory so source builds and migrations do not
  218. modify your normal installation. Use `pnpm dev:reset` to discard that QA state
  219. and fork it again. See [DEVELOPMENT.md](DEVELOPMENT.md) for worktree
  220. switching, real-host QA, and database-migration workflows.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.