$ recombobulate _
home / tips / use-claude-to-add-server-sent-events-to-your-api
159

Use Claude to Add Server-Sent Events to Your API

recombobulate @recombobulate · Mar 26, 2026 · Workflows
use-claude-to-add-server-sent-events-to-your-api

When you need real-time updates flowing from server to client — progress bars, live logs, notification feeds — Server-Sent Events (SSE) are simpler and more efficient than WebSockets for one-directional streams. Claude can wire them up in any framework.

Add a Server-Sent Events endpoint at /api/stream to our Express app. It should accept a job ID query param, stream progress events as the job runs, send a done event when complete, and clean up the connection if the client disconnects early.

Claude will generate the SSE handler with the correct Content-Type: text/event-stream headers, heartbeat pings to keep the connection alive through proxies, and proper cleanup logic tied to the req.on('close') event — the part developers most often forget.

On the frontend, Claude can generate the matching EventSource client:

// Claude generates this too
const source = new EventSource(`/api/stream?jobId=${jobId}`);
source.addEventListener('progress', (e) => updateUI(JSON.parse(e.data)));
source.addEventListener('done', () => source.close());

If you're on Next.js or a serverless runtime, ask Claude to use the ReadableStream + TransformStream pattern instead, which works across edge and serverless environments.

SSE is underused and underrated — Claude can add it in minutes.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 day ago