development

Portless setup for Next.js maps the tool-resolved origin into your existing application-origin environment variable before launching the dev server. Application code and schemas stay unaware of the proxy, and a direct next dev command is preserved alongside the wrapped script.

Each checkout receives its own resolved identity so concurrent worktrees get distinct origins without collisions. The setup verifies two simultaneous instances, confirming each app's configured origin and callback destinations match its own checkout.

Yes, Express, Hono on Node.js, and other Node.js HTTP servers are supported through the Node.js mapping. It traces the actual listener to prove the assigned port reaches the listen call, since environment injection alone does not configure a hardcoded listener.

Yes, Turborepo workspaces are supported by keeping task ownership inside package scripts and retaining the existing root orchestrator. Development tasks stay non-cached with long-running lifecycles, and environment filtering is resolved where values are actually injected.

Production deployment is explicitly out of scope, and the skill does not author missing convention documents or install unrelated skills. It also avoids creating sample applications just to claim verification, reporting anything that could not be exercised.

A working local hostname does not prove the authentication provider accepts it, since providers enforce their own callback URL registrations. The setup checks provider callback restrictions, cookie scope, and trusted-origin behavior against the actual resolved origin.