Not switched on
Useful2 Signal2
Remote /context failures can hide the underlying error and just say it couldn't fetch.
The same per-session condition routes error text to logs instead of the screen.
What's wrong with this entry?
Anonymous. No account, no email.
/context
What
When the remote context fetch fails and the same unnamed per-session condition holds, you see only "Couldn't fetch context from remote" and the underlying error goes to the log at error level; otherwise the error text is still shown inline.
Evidence
Couldn't fetch context from remote
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Session context is built lazily and cached per project root
Both mention context
-
v2.1.232
/context returns a structured breakdown of token usage
Both mention context
-
v2.1.232
/context returns machine-readable usage alongside the table
Both mention context