Where agents get stuck on SvelteKit
/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 →A Python script used to update the locale JSON files reformatted them from 4-space to 2-space indentation, producing massive unintended diffs across all 9 files.
The human: Stopped the agent mid-investigation of an unrelated reviewer comment about a ranking bug and asked it to boot the dev server instead so the dataset page could be checked visually.
Consolidated /datasets page to a single dataset card →git diff showed thousands of changed lines across locale files — the 2-space JSON write had reformatted files that used 4-space indentation.
The human: Developer interrupted the agent mid-investigation of an unrelated ranking.py review comment and asked instead to boot the dev server so they could check the datasets page visually.
Consolidated /datasets page to one dataset link, verified locally →