Dev server
Run your project beside the chat, so every change Panda makes shows up in the preview a few seconds later.
Feature Updated 20 Nov 2026What a dev server is
A dev server is the command that runs your project while you work on it, such as npm run dev. PandaOS starts it for you and points the preview at it. Ask for a change, Panda edits, and the preview updates beside the chat a few seconds later.
Set one up
A project with no dev server shows a dim Set up dev server button in the dock. It opens the Dev servers tab of the project settings. When PandaOS recognises the project it suggests a command when you add it, so this is often done already. The dev server shows only in projects with coding tools on.
- Open the project overview and press Project settings, then the Dev servers tab.
- Fill in the Command.
PandaOS suggests one from your package manager when it recognises the project. Accept it or write your own. - Set the Port it listens on.
It has to match what your command serves on, because that is where the preview points. - Press Save.
Start, stop and restart now appear in the dock.
What you can set
Each server on the Dev servers tab has a Name, a Command, a Port and a Working directory relative to the project folder. An optional Install command is what the Install button runs. The port is passed to your command as the PORT environment variable.
- Auto-start starts the server when the project opens.
- Keep running after PandaOS quits leaves it up when you close the app. Without it, the server stops with PandaOS.
Press Add server for a second one. A project can run several at once, each with its own command, port and folder. That is what a monorepo needs: the web app on one port, the API on another.
Reading the indicator
The dev server indicator in the dock shows the state and the actions it offers.
| State | Colour | Actions |
|---|---|---|
| Stopped | Grey | Start |
| Starting... | Yellow, pulsing | Stop, Restart |
| Running | Green | Stop, Restart, Open in browser |
| Error | Red | Start |
| Port in use | Orange | Kill & Restart, which stops the program holding the port and starts your server |
| Port used by another project | Grey | Open in browser |
| Port used by another app | Grey | Open in browser, Kill & Restart |
Ports
A new project gets the next free port, counting up from 3001. Change it on the Dev servers tab, or in the setup dialog when you add the project.
Secrets the server needs
Keys and passwords for your server live in the Credentials panel: the .env files PandaOS finds, with values hidden until you reveal them. Panda reads and writes them there rather than opening the file, so a value is never printed into the chat.
How the command is suggested
When you add a project, PandaOS reads package.json and recognises these frameworks:
| Framework | Detection |
|---|---|
| Next.js | next in dependencies |
| Nuxt | nuxt in dependencies |
| SvelteKit | @sveltejs/kit in dependencies |
| Remix | @remix-run/react or @remix-run/dev in dependencies |
| Angular | @angular/core in dependencies |
| Astro | astro in dependencies |
| Vite | vite in dependencies |
| Svelte | svelte in dependencies |
| React (CRA) | react-scripts in dependencies |
| Vue | vue in dependencies |
| React | react in dependencies |
| Express | express in dependencies |
| Fastify | fastify in dependencies |
| Hono | hono in dependencies |
PandaOS looks in both dependencies and devDependencies. Detection follows the order of the table, so a project with both Vite and Next.js is detected as Next.js.
The suggested dev command does not depend on the framework. PandaOS takes the first of the dev, start, serve and develop scripts that your package.json defines and runs it with your package manager. That is npm run dev or npm start with npm, and pnpm dev, yarn dev or bun dev otherwise. A project with none of those scripts gets no suggestion.