v0.4.4

What's Changed

• Fix CA trust on macOS: Trust the devproxy CA in the login keychain (~/Library/Keychains/login.keychain-db) instead of the system keychain. No more sudo required. curl, reqwest/native-tls, and browsers now trust devproxy HTTPS URLs automatically after devproxy init.

v0.4.3

What's New

• devproxy restart command — Restart the devproxy daemon with a single command. Wraps the existing platform-managed daemon restart (launchd/systemd).

v0.4.2

New Features

devproxy get-url command

Prints the current project's proxy URL to stdout. Designed for scripting:

• Exits 0 with the URL if the project is running
• Exits 1 with no output if not running

URL=$(devproxy get-url)

/devproxy:url plugin skill

Claude Code plugin skill that uses get-url to discover the current project's proxy URL on demand.

v0.4.1

Bug Fix

Fix: devproxy --version killed by launchd

The launchd plist pointed at the same binary path users invoke (~/.local/bin/devproxy), causing KeepAlive=true to SIGKILL any CLI invocation. The daemon binary is now installed at a separate path (~/Library/Application Support/devproxy/devproxy-daemon on macOS), preventing launchd from interfering with normal CLI usage.

What changed

• devproxy init copies the binary to a dedicated daemon path
• devproxy update updates both CLI and daemon binaries
• Plist/unit files reference the daemon binary, not the CLI binary

v0.4.0

What's New

App-named slugs

Slugs now include the app name derived from git remote origin (directory name fallback), formatted as {random-slug}-{app-name} (e.g. swift-penguin-devproxy). This makes it easy to identify which project a URL belongs to, while still supporting multiple worktrees of the same repo via the random slug prefix.

devproxy ls current-directory indicator

devproxy ls now marks the current directory's project with *, so you can quickly see which URL belongs to your cwd.

Other improvements

• Dynamic column width in ls output for long URLs
• DNS label length enforced (63 char max)
• 13 new unit tests

v0.3.0

What's New

User-owned daemon via socket activation

• macOS: launchd socket activation via LaunchAgent — daemon runs as your user, no sudo needed for devproxy init
• Linux: systemd socket activation with setcap fallback — same no-sudo experience
• sudo is only needed for one-time DNS setup and CA trust, not daemon startup

Platform lifecycle management

• devproxy update now uses platform-aware restart (launchctl kickstart / systemctl restart)
• LaunchAgent plist and systemd unit file generation with proper environment propagation
• Propagates user PATH to LaunchAgent for Docker access

Testing

• Docker-based Linux e2e tests for systemd, LISTEN_FDS protocol, and setcap paths
• Improved test isolation with DEVPROXY_NO_SOCKET_ACTIVATION

v0.2.0

Version bump for testing self-update

v0.1.0

First release with self-update command and macOS Gatekeeper fix

v0.0.4

What's New

• Claude Code plugin: devproxy can now be installed as a Claude Code plugin (claude plugin add foundra-build/devproxy), giving Claude contextual knowledge about installing, configuring, and using devproxy for local HTTPS dev subdomains.

v0.0.3

What's Changed

• Fix daemon setup flow: stale cleanup, timeouts, improved init output by @willisrocks in #3

Full Changelog: v0.0.2...v0.0.3