This is the fastest path for a developer who wants StacyVM running locally.Documentation Index
Fetch the complete documentation index at: https://docs.stacyide.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Start StacyVM
Run this in a fresh terminal:http://localhost:7423.
You still need Docker Desktop or Docker Engine running locally. If Docker is not reachable, setup stops and prints the fix for your operating system.
Clean Verification Flow
Use this flow when you want to verify each step before starting the server.1. Verify The Npm Package
2. Run Setup Without Starting The Server
This checks clone, dependency installation, Go module download, and build behavior safely.3. Start StacyVM
4. Check Health
In a second terminal:5. Create A Sandbox
6. Run Code
7. Destroy The Sandbox
8. Optional Full One-Command Run
After the verification flow passes:Common Fixes
Docker CLI is installed, but the daemon is not reachable
Docker CLI is installed, but the daemon is not reachable
Start Docker, then verify it:On macOS, start Docker Desktop:On Windows, run setup inside WSL 2 Ubuntu and enable Docker Desktop WSL integration for that distro.
Go is missing
Go is missing
Install Go, then rerun setup.macOS:Ubuntu or Debian:
Port 7423 is already in use
Port 7423 is already in use
Check what is listening:Stop that process, or use the StacyVM server that is already running.
You only want to test clone and build
You only want to test clone and build
Skip server startup:If Docker is not running yet, you can also skip Docker validation:
Next Steps
- Use the Quickstart for SDK and REST examples.
- Review Core Concepts when you want the mental model.
- Use Production Deployment before exposing StacyVM to other users.

