Tier 1: Local Development

Tier 1: Local Development

Tier 1 gives the agent enough runtime access to help with everyday coding and debugging on your machine.

You Provide / Confirm

• The repository entrypoint and the services you want the agent to own.
• The browser-debug boundary for local loopback frontends.
• Optional non-sensitive auth_hint guidance that explains login or token flow.
• Optional debug_credentials for test accounts, passwords, or service API keys the agent is allowed to read.

The Agent Does

• Creates or updates the SuperDev project model after inspecting the repository.
• Probes language runtime providers, then generates and validates local service runtime / deployment config.
• Previews config changes before writing them and waits for approval when required.
• Uses start_service, stop_service, and restart_service for managed services.
• Reads logs with tail_logs, search_logs, and get_log_context.
• Opens local browser sessions with list_browser_targets -> open_browser_debug_session -> browser_snapshot -> browser_*.
• Uses list_code_debug_targets -> debug_capture_at when logs and diagnostics are not enough.
• Calls get_debug_credentials when it sees credential hints and needs to pass authentication.

Boundaries

If a project is managed by SuperDev, the agent should not start its own npm run dev, go run, or tail -f process. That creates orphan processes and splits runtime truth.

Browser debugging covers local loopback frontend deployments, not arbitrary public websites or your personal browser profile. browser_evaluate is disabled by default and must be enabled by the user because it can read page storage and cookies.

Code debugging is a last resort. debug_capture_at attaches to a running process; it does not restart the service just to enter debug mode.

Next

• Agent owns runtime
• Debug credentials
• Language Runtime Provider