Develop and run your app locally

Run the generated application from a workspace you control. Use a stdio connection with a local target.

1. Open the project directory and connect MCP.
2. Verify session_status reports the intended local workspace.
3. Call local_status to inspect prerequisites.
4. Call local_setup_guide and follow the project’s specific setup instructions.
5. Supply a database and Valkey service when the app requires them. Use set_local_service to record the selected addresses through the supported interface.
6. Call run_local with the intended build choice.
7. Open the resulting local address and try the main workflow.
8. Use stop_local when you want to stop that app.

A local database keeps records on the service you choose. A local app does not automatically copy the hosted preview’s records or credentials.

Review generated configuration before inserting private connection URLs. Keep secrets out of shared client configuration and source commits.

The hosted HTTP endpoint cannot start processes on your machine. If a local tool is absent, verify the connection uses stdio and --target local.

Keep the project harness with the source and ask the coding agent to follow it when developing a story. See local runtime tools.

Names and marks

OpenAI, ChatGPT and related OpenAI marks belong to OpenAI; Codex is an OpenAI product. Usage policy.

Claude and Claude Code are Anthropic products; their names and marks remain with their respective owner. Usage policy.

Valkey is a Linux Foundation project. Its name and marks are used to identify the referenced technology. Usage policy.

Node.js, npx names and any associated marks remain with their respective owners or project maintainers. References identify products, standards or source examples. OwlMeans documentation does not imply sponsorship or endorsement by those owners.