Help us improve
Share bugs, ideas, or general feedback.
From wasp
Starts Wasp dev server with database setup (SQLite or Postgres via Docker), server logs access, and browser console integration for debugging client/server issues.
npx claudepluginhub wasp-lang/wasp-agent-plugins --plugin waspHow this skill is triggered — by the user, by Claude, or both
Slash command
/wasp:start-dev-serverThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- [ ] Ask the user if they want to start the dev server(s) as a background task in the current session, or on their own in a separate terminal:
Configures Replit dev workflow: .replit run commands, hot reload for Node/Python/Vite, Webview ports, dev/prod DBs, Replit Agent.
Displays Wasp plugin's features, commands, skills, and initialization status. Lists skills like add-feature, start-dev-server, and example prompts for Wasp app workflows.
Starts a local development server with Flask backend and MCP server, including port selection, cache-busting, auth bypass, and CSS hot-swapping.
Share bugs, ideas, or general feedback.
background tasks tab.Grep the .env.server file for DATABASE_URL. If no line starts with DATABASE_URL, continue following this step.
If the user does have their own DATABASE_URL env var set, move on to Step 2.
Check the schema.prisma file in the project root for the datasource block to see which database is being used.
Skip to Step 2: SQLite stores data in a local file, no database server needed.
Start the managed database container as a background task:
wasp start db
Docker needs to be installed and running for the managed Postgres database container (wasp start db) to work.
Run this as a background task in the current session. Wait 5-15 seconds for the database to be ready.
Start the Wasp development server as a background task:
wasp start
If this is the first time starting the app, or if there are pending migrations, run the following command:
wasp db migrate-dev --name <migration-name>
Confirm client (localhost:3000) and server (localhost:3001) are running by checking the background task output.
If started as background task in current session: Listen to the output for development and debugging information. If started externally: Instruct the user to check the output of the external terminal and share its output with you.
This step is critical for effective development and debugging. Without browser console access, the agent cannot see client-side errors, warnings, or React issues that occur in the browser.
Ask the user (via the AskUserQuestion tool) which method they'd like to use for giving the agent visibility into the browser console:
| Option | Description |
|---|---|
| Chrome DevTools MCP (recommended) | Must be installed |
| Built-in Chrome | Use Claude Code's built-in browser connection (check status with /chrome command) |
| Manual | User will manually copy/paste console output when needed |
| Other | User has another preference |
For the Chrome DevTools MCP option, if not already installed, add the following config to their mcp client:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}