devproxy
Local HTTPS names for services running in Git worktrees.
devproxy gives each Git worktree a predictable local HTTPS URL, such as https://kasta-feature-login.localhost. Caddy handles TLS and forwards requests inside the devproxy daemon by default. The daemon manages routes, while the CLI starts or registers development services. Application traffic goes through Caddy.
This is an early local development tool for macOS and Linux. Services run on the host, or in a container with their HTTP port published to the host.
Get started
Build the CLI, start the proxy, and open your first service.
Use it in a project
Wrap project scripts and install the agent skill.
CLI reference
Commands, flags, and environment variables.
Routes and URLs
Worktree names and shared origins.
Troubleshooting
Resolve startup, TLS, and registration problems.
Architecture
Open the diagram on its own page.
Dashed arrows show startup and route control. The browser's application requests follow the solid path through Caddy to the development service; they do not pass through the devproxy daemon. Caddy also forwards https://devproxy.localhost to the daemon's dashboard.
How it works
- Caddy owns local HTTPS and proxies requests to services on
127.0.0.1. devproxy startlaunches one background process for Caddy, the dashboard, and the control API on127.0.0.1:7654. It loads active routes through Caddy's Go API. External Caddy remains available through its local admin API.devproxy runstarts a development command on a free port, ordevproxy registerattaches an existing service. Both keep their registrations alive while they run.
Open https://devproxy.localhost to see active services, or run devproxy list.