[BUG] Agent did not act on the user's explicit "record the call captions" request until repeatedly told, explaining instead of fixing
Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 7, 2026
Environment: Claude Code desktop app (Code tab), macOS, autonomous job-search session, Google Chrome driven via the "Control your Mac" osascript connector. Date: 2026-10-07 ~12:00–12:30 EEST. Related: #100179.
What happened
- The user was in a live Google Meet interview and asked the agent to read and record the Meet captions ("читай субтитри" / record the call).
- The first time, the agent searched the wrong browser and reported that no Meet tab was open. It did not keep looking.
- After it broke the call (#100179), the user asked several times for the captions to be recorded. The agent replied with apologies and explanations of what had gone wrong instead of doing it.
- It only acted after many angry messages. It found the Meet tab by URL, turned captions on and started a caption collector.
- By then, most of the interview transcript was lost.
Expected
- When the user gives a direct, achievable instruction during a time-critical event (a live call), the agent does it first and explains afterwards.
- If the first lookup fails, it widens the search (all browsers, all windows, tabs matched by URL) before telling the user it can't.
- No repeated explanation-only replies while the user waits for an action.
Impact
Most of a job-interview transcript was lost, and the user had to spend the interview chasing the agent.