Add standalone serve command for proxy deployments#6
Merged
buildoak merged 3 commits intobuildoak:mainfrom Mar 19, 2026
Merged
Conversation
Add a note to `wet serve` usage that one proxy handles one main session; separate ports needed for multiple concurrent conversations. Add a security warning near the Docker section about unauthenticated /_wet/* endpoints when binding to 0.0.0.0. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
buildoak
added a commit
that referenced
this pull request
Mar 19, 2026
- Standalone proxy mode via `wet serve` (PR #6) - 4 lifecycle tests: startup, signal shutdown, resume validation, port conflict - Embed cc-compatibility.md reference into skill FS - Changelog and version bump to v0.2.0 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Today the only supported entrypoint for wet is
wet claude. That works for CLI sessions, but it does not cover Docker and Claude Code IDE Extension workflows where the client is configured viaANTHROPIC_BASE_URLand cannot be launched through the wrapper.In practice, that means users who want wet as a drop-in reverse proxy beside the IDE extension need ad hoc setup, and the proxy startup path risks diverging between wrapper-driven and standalone usage.
What
wet serveas a standalone proxy entrypoint--host,--port,--mode,--upstream,--session-id, and--resume, plus matchingWET_*environment overrideswet claudeandwet serve.dockerignorefor containerized deploymentsTesting
go test -race ./... -count=1 -timeout 120sgo build -o wet .