This page collects the setup issues users are most likely to hit.
Use npx:
npx @waishnav/devspace init
npx @waishnav/devspace serveIf you installed globally, confirm npm's global bin directory is on PATH.
DevSpace requires Node >=22.19 <27.
Check:
node --versionInstall Node 22 LTS with your preferred version manager such as nvm, fnm, or
mise.
This usually means native dependencies were installed under a different Node runtime.
Try:
npm rebuild better-sqlite3Then run:
npx @waishnav/devspace doctorRelease starts run a native dependency check before launching.
Use the origin for setup:
https://your-tunnel-host.example.com
Use the MCP endpoint in the client:
https://your-tunnel-host.example.com/mcp
If you saved the wrong value:
npx @waishnav/devspace config set publicBaseUrl https://your-tunnel-host.example.comTemporary tunnels often change URLs between runs.
For a one-off run:
DEVSPACE_PUBLIC_BASE_URL="https://new-tunnel.example.com" npx @waishnav/devspace serveFor a stable URL:
npx @waishnav/devspace config set publicBaseUrl https://devspace.example.comDevSpace derives allowed hosts from the configured public URL.
Run:
npx @waishnav/devspace doctorConfirm the public URL hostname appears in allowed hosts. If you changed tunnel
URLs, update publicBaseUrl.
Use this only for intentional local debugging:
DEVSPACE_ALLOWED_HOSTS="*" npx @waishnav/devspace serveBy default, DevSpace allows redirects for:
chatgpt.com
localhost
127.0.0.1
If another MCP client uses a different redirect host, configure:
DEVSPACE_OAUTH_ALLOWED_REDIRECT_HOSTS="chatgpt.com,example.com" npx @waishnav/devspace serveMake sure you are entering the Owner password from:
~/.devspace/auth.json
To regenerate setup:
npx @waishnav/devspace init --forceworkspaceId values are session identifiers. If the server restarts and the
client receives an unknown workspace error, call open_workspace again for that
project.
Workspace session metadata is persisted, but clients should still treat
open_workspace as the way to begin a fresh working session.
The path must be inside one of the allowed roots configured during setup.
Run:
npx @waishnav/devspace config getThen either open a project under an allowed root or rerun setup:
npx @waishnav/devspace init --forceWorktree mode requires:
- Git installed
- the path is inside a Git repository
- the repository has at least one commit
- the requested
baseRefresolves to a commit
For a new repository, create the first commit or use checkout mode.
Uncommitted source checkout changes are not copied into the managed worktree. Commit, stash, or ask the model to work in checkout mode if those changes are needed.
DevSpace shell execution requires Bash. Native PowerShell and cmd.exe command
execution are not supported yet.
Install Git for Windows and use Git Bash, or use WSL, MSYS2, or Cygwin Bash.
Run:
npx @waishnav/devspace doctorConfirm Bash is detected.
Skills are enabled by default. Check:
DEVSPACE_SKILLS=1 npx @waishnav/devspace serveDevSpace looks in:
DEVSPACE_AGENT_DIR, defaulting to~/.codex- project
.pi/skills DEVSPACE_SKILL_PATHS
If a skill appears in open_workspace, the model must read that skill's
SKILL.md before reading other files inside the skill directory.
Per-tool widget cards are enabled by default with:
DEVSPACE_WIDGETS=fullThe aggregate show_changes tool is only exposed with
DEVSPACE_WIDGETS=changes. Plain MCP clients may ignore ChatGPT Apps widget
metadata and only show text results.