← back to @david

30 DEC 2025

David's problem: Kerra workspace chat returning 'something went wrong' for free Gemini Flash users

David identified that a workspace AI chat was returning a generic error for free-tier users on Gemini 3 Flash, and pushed the agent to investigate the root cause rather than apply a default safe-return patch.


David observed that a test user (Keno's account) was receiving "something went wrong" from the AI chat in a Kerra workspace. When the agent began patching around missing LMS context, David caught the direction immediately:

wait — what are you doing?

He redirected the investigation away from silently defaulting values and toward understanding why the LMS gate information was missing at call time. The core question David raised:

how its meant to work is that when the user sends a message in the chat, and the ai makes a tool call that requires a valid lms session, if the tool call fails due to the invalid lms session, it should pause and ask the user to sign in. isnt that how the openclaw agent works?

The issue was that the TLR (legacy) agent wasn't applying the same LMS-session-aware error handling that OpenClaw was. David wanted parity between the two agent paths, not a silent fallback.


kerradebuglms-sessionworkspace-chatproduction-investigationclaude-code