How to use Claude to build a Go WebSocket proxy
Claude Code implemented a Go proxy exposing an HTTP request/callback interface over a WebSocket-only service, then tested it live and fixed review findings.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Read [service API documentation] and help build a Go proxy exposing [HTTP request/callback interface] over its persistent WebSocket API. Discuss architecture and libraries with me, save a phased plan, test each phase and the live service, then review with fresh context.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- wrs
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reported completion in two hours, passing phase tests, live protocol debugging, and a race-condition fix after review.
- Human involvement
- The author discussed architecture and library choices and requested live tests plus two fresh-context reviews.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Read the service API documentation and discuss architecture and libraries.
- Save a phased implementation plan in Claude Code plan mode.
- Implement four phases with passing tests for each.
The author needed a request-and-callback HTTP API for a third-party service whose official API used persistent WebSocket connections. They created a new directory and described the desired Go proxy to Claude Code. Before implementation, they had it read the service's API documentation and discussed architecture and library choices with it.
Claude Code saved a phased implementation plan in plan mode. It then implemented the proxy in four phases, with passing tests for each phase. The work also included live tests against the service. During those tests, Claude Code used curl to debug protocol mistakes rather than relying only on the earlier test results.
Finally, the author requested two rounds of code review with fresh context. Those reviews led to a race-condition fix and some cleanup. The author reported a total elapsed time of two hours. Their account emphasizes direction at a high level: they established the problem, discussed the design, and explicitly requested planning, testing, and review.
Who it's for: Developers adapting a WebSocket-only service to an HTTP workflow who can guide architecture and evaluate live integration behavior.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · wrs
Frequently asked questions
What testing did the author report?
Claude Code completed four phases with passing tests for each, then ran live tests against the service and debugged protocol mistakes using curl.
What did the reviews change?
Two fresh-context code-review rounds led to a race-condition fix and some cleanup. The author reported two hours for the overall work.
More details
Remaining steps
- Run live service tests and debug protocol mistakes using curl.
- Perform two fresh-context reviews and fix the race condition.
About this account
Claude Code planned, implemented, tested, debugged, and revised the proxy under explicit author direction.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=47479761. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: wrs on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Go · curl
Software development
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.