Project helpers
Use a lifecycle process when the project needs a long-running host helper, such as a development tunnel or database proxy. Use an up-before hook for a finite setup or authentication check. This makes the dependency visible in project configuration instead of relying on an extra terminal tab.
Read Lifecycle for this version's concrete configuration schema and examples. Keep tool installation separate from login: a cloud SSO login may require the person to complete its browser flow, and credentials must not be committed or printed. Check the approved CLI profile and target before starting a tunnel. A listener existing on a port does not prove it is the correct tunnel.
Declare readiness and ownership using the supported lifecycle contract. Reuse an existing healthy listener only when the configuration explicitly supports adoption; shutdown must preserve externally owned processes. Confirm the helper's expected connection and the app's health after startup. No tunnel, public endpoint or cloud login is created by reading this guide.