Manage development services

Keep a development service visible#

Manage a local preview or API through the conversation and inspect its process, port, logs, and lifecycle in the Activity Panel.

Find the real start command#

Confirm the project's command, directory, port, and dependencies. Check for an existing preview first. If a port is occupied, identify its owner rather than stopping an unrelated process.

This guide covers local development services in 1.1.22. Starting a preview is not a production deployment.

Start a project preview#

1. Ask the agent to inspect the command and existing preview.
2. Authorize the specific development command if a new service is needed.
3. Inspect the service in the Activity Panel, then open its actual URL.

Inspect this project's development command and expected port.
Reuse an existing healthy preview belonging to this project.
Otherwise start the agreed command as a managed development service.
Do not stop unrelated processes or change environment files.
Report the process, readiness result, and preview URL.

Verify and manage the lifecycle#

Success means the command runs in the right project, the port is ready, and the browser shows the intended app. For a worker without a port, use its logs or a project-specific readiness check.

Stop or restart only the identified service you own. After reopening the app, recheck the process and readiness even if its record was restored.

Troubleshoot startup#

• Immediate exit: read the startup error and check dependencies.
• Port not ready: inspect configuration, pending input, or dependent services.
• Wrong app appears: check port ownership and URL.
• Page fails: inspect service logs and browser console/network evidence. Logs have retention limits, so save relevant evidence promptly.

Use the preview#

Test the page with browser automation. See files, terminal, and Review for edits and permissions for additional access.