pkg/log produces flat log lines with no per-request identifier. When multiple HTTP-mode clients are calling tools concurrently, lines from different requests interleave with no way to correlate "this error" with "that tool call".
Suggested direction
In the HTTP middleware (and stdio loop), generate a short request ID (8–12 chars) and store it in ctx
Have pkg/log read it from ctx and prefix every line
Echo the same ID in the outgoing X-Request-ID header to Gitea so server-side logs can join up
## Problem
`pkg/log` produces flat log lines with no per-request identifier. When multiple HTTP-mode clients are calling tools concurrently, lines from different requests interleave with no way to correlate "this error" with "that tool call".
## Suggested direction
- In the HTTP middleware (and stdio loop), generate a short request ID (8–12 chars) and store it in `ctx`
- Have `pkg/log` read it from `ctx` and prefix every line
- Echo the same ID in the outgoing `X-Request-ID` header to Gitea so server-side logs can join up
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
pkg/logproduces flat log lines with no per-request identifier. When multiple HTTP-mode clients are calling tools concurrently, lines from different requests interleave with no way to correlate "this error" with "that tool call".Suggested direction
ctxpkg/logread it fromctxand prefix every lineX-Request-IDheader to Gitea so server-side logs can join up