星云节点

Quickstart

Use Python 3.12 and Node.js 24. Install FFmpeg (ffmpeg and ffprobe on your PATH) for video processing and QC.

git clone https://github.com/JustinPerea/nebula-nodes.git
cd nebula-nodes

Terminal 1 — backend, from the repository root:

python3.12 -m venv backend/.venv
backend/.venv/bin/python -m pip install -r backend/requirements.txt
backend/.venv/bin/python backend/devserver.py --port 8000

It prints a link like http://localhost:5173/#nebula-person=…&backend=http://127.0.0.1:8000 (add --open to open it in your browser instead). That link connects the canvas as you: only a tab opened from it can change Settings, keys and connections, accept agent proposals and start agent chats. The token lasts until the backend stops, and survives code reloads. A tab opened without it still works for building and running, with those actions locked. Agents that reach Nebula only through its MCP server, CLI or API don't get the token, so they stay held to the spending limits. That covers the in-app agents: Claude and Codex (its shell has no network; it reaches Nebula through the Nebula MCP server). Personal agents get a per-session token in the shared outside budget instead (docs/PERSONAL-AGENTS.md). Anything with its own unsandboxed shell can still read the token from your browser's storage (see docs/MCP-SETUP.md and In-app agents use this server).

Terminal 2 — frontend, from the repository root:

npm --prefix frontend ci
npm --prefix frontend run dev -- --host 127.0.0.1 --port 5173

To run a second copy next to this one (for tests or screenshots), see Running a second, isolated dev instance; otherwise it can find and write to the backend on port 8000.

Open the link from Terminal 1, then add the provider keys you need in Settings (the gear at the top right of Projects, or the bottom of the left rail inside a project). Provider usage is billed to your accounts. Browser mode stores keys in the gitignored, plaintext settings.json; the macOS desktop app uses Keychain encryption. Neither reads keys from your shell: devserver.py and the app both drop provider key variables like OPENAI_API_KEY from the backend's environment, and devserver.py prints the names it ignored.

Try a Text Input → GPT Image 2 → Preview graph and hit Run. Generated files go to output/ by default; change the location in Settings → Storage.

Prefer an app? On an Apple silicon Mac, build Nebula.app once and open it from Applications or the Dock; it starts the backend itself and stops it when you quit:

cd desktop && npm install && npm run package && npm run install-app

It runs this checkout (so git pull updates it; rebuild the renderer with cd frontend && npm run build:desktop after frontend changes) and keeps its own data in ~/Library/Application Support/Nebula Nodes/. The first launch copies your browser-dev data and API keys there (copy only, nothing is deleted), but only when that folder has no migration-state.json yet. If an earlier desktop run already left one, the copy is skipped: the app opens with that older data and asks for your API keys again, so add them in Settings (they go to the Keychain). To start fresh from browser dev instead, quit Nebula and move ~/Library/Application Support/Nebula Nodes aside (rename it, say to Nebula Nodes.old; don't delete it), then open Nebula again. After the first launch the app and browser dev have separate projects, outputs and settings. The two terminals above stay the way to develop. Details, signing and Gatekeeper notes: desktop/README.md. Agent chat and Paper are optional; configure them when you need them.