Shawnaldinho wants every broken chat to come with a tracking number
A proposal to give the backend a proper paper trail so a failure a user sees can be traced back to the exact line that caused it.
Right now the backend's logs are free-form scribbles, so an error a user hits on screen can't be tied back to what actually went wrong on the server, and there's no clean way to sort logs by route, status, or user. Shawnaldinho's open proposal lays a foundation:
- A structured logger that writes clean, filterable log entries instead of loose text.
- A unique ID stamped on every request and handed back to the client, so one failing action can be traced end to end.
- A single summary line per response recording the route, outcome, timing, and user.
- Cleanly telling apart a user who cancelled from a genuine server error, without guesswork.
The headline win: the app could show a user their request ID, so a "my chat broke" report arrives with the exact token support needs to find it. Broader cleanup is deliberately left for later.
So what Anyone who runs support or reliability for a legal-AI product should watch this - it's the difference between chasing a vague complaint and pulling up the exact failed request.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?