Use devproxy in a project

Wrap a development commandCopy Anchor Link

Build the devproxy binary and put it on your PATH, then run a project's development command through devproxy run. Use one stable --project name across all of the project's worktrees. Run the wrapper from the Git checkout so it can derive the worktree name.

devproxy run --project kasta --url-env NEXT_PUBLIC_APP_URL web -- next dev -p '{port}'

The command starts Next.js on the chosen port and gives it PORT, DEVPROXY_URL, and NEXT_PUBLIC_APP_URL. The worktree's URL is https://kasta-<worktree-folder>.localhost. Keep the wrapper running while using the app.

If a project's dev script already wraps devproxy, run that script directly. The Kasta root uses pnpm dev after devproxy start; its web script registers the worktree and sets NEXT_PUBLIC_APP_URL automatically.

See Routes and URLs when an API and frontend should share an origin. For an existing service that controls its own port, use devproxy register.

Install the agent skillCopy Anchor Link

The repository includes skills/devproxy/SKILL.md. It tells a coding agent how to start a devproxy project, find its URL, and list active services. From the project that will use devproxy, install it with the skills CLI:

npx skills add /absolute/path/to/devproxy --skill devproxy

Select the agent you use when prompted. The skill is installed in that project, so new agent sessions can use it. To install from GitHub, run npx skills add vietz-dev/devproxy --skill devproxy instead.