Stack · 2 sessions

elysia sessions with coding agents

2 sessions on elysia with a coding agent: the agent failed at least once in 2, and 0 finished without a human stepping in.

More filters →

Claude Code·feature·Web·library1d

Built an Elysia + SvelteKit stack for browsing ORV databases, then stalled on a 404 routing bug

Takeaway: Next time I'd nail down the SvelteKit server-fetch/env-var pattern up front instead of letting the agent iterate through three different fixes for the same root cause.

1h 08m2interventionsBun elysia SvelteKit0 cmt

Claude Code·feature·Web·library1d

Built bun/Elysia backend and Apple-styled SvelteKit frontend for ORV wiki, but left routing bug unresolved

Takeaway: Next time I'd tell it upfront to use a single server-side fetch helper (or a proxy +server.ts route) instead of env vars for backend URLs, since that's what ate an hour of back-and-forth.

1h 08m1interventionBun elysia SvelteKit0 cmt

Where agents get stuck on elysia

/db/orv returned 404 in the frontend; repeated attempts to fix the BACKEND_URL env var (moving it into the load function, checking .env loading) did not resolve it

The human: Agent tried to read files to diagnose the mismatch; developer rejected the tool call, saying they'd manually renamed the route directory to [slug] which didn't match the code's params.name, then interrupted the session

Built bun/Elysia backend and Apple-styled SvelteKit frontend for ORV wiki, but left routing bug unresolved →

After the env-var fix, /db/orv still returned 404 in dev — $env/dynamic/private wasn't resolving, and a top-level const evaluation bug made it worse even after moving it inside the load function

The human: Rejected the agent's next tool call and pointed out they had manually renamed the route folder to [slug] themselves, which was actually the real source of the mismatch — then cancelled the request

Built an Elysia + SvelteKit stack for browsing ORV databases, then stalled on a 404 routing bug →