Lane environment

Ports, environment variables, startup commands, and preview links for lane-scoped work.

Each lane can have its own runtime environment. This keeps parallel tasks from fighting over ports, credentials, and local state.

What can vary by lane

Area	Example
Port	Lane A uses 3001, lane B uses 3002.
Environment variables	A lane points at a test database or feature flag.
Startup command	A lane starts npm run dev or another local server.
Preview URL	A clickable local URL opens the lane’s running app.

Basic setup

1. Create or select a lane

   Open the lane that needs custom runtime settings.

2. Open environment settings

   Add only the variables or command overrides that are specific to this lane.

3. Start the process

   Use Run or the lane terminal to start the app.

4. Verify the preview

   Open the preview URL and make sure it points at the selected lane.

Keep it simple

• Prefer project defaults until a lane truly needs an override.
• Never paste production secrets into lane settings.
• Use clear variable names and document unusual overrides in the lane prompt.
• Stop unused lane processes so ports return to the pool.

Agents inherit the lane environment when they run commands. If a test depends on a lane-specific variable, mention that in the prompt.