1.40.0 — click to answer in Claude Code, and “needs you” only when it is real

• “Needs you” only when a session really asks. The visitor, the red line, the sound and the notifications (VS Code, the desktop app, the status bars) now come only when Claude Code or Mistral Vibe says a question or a permission menu is open. A call left without its answer (you typed something else, the session was closed mid-call) no longer reads as waiting for you, and a session Claude Code says is at work is believed. A question in a session started with claude -p goes to the program that started it, not to you: it never needs you. Where Claude Code does not say (Cowork, Claude Code before 2.1.269), a question or a plan open in the transcript still needs you, and a file edit left pending is only a guess: it stays on the tile as “needs you?”, with no visitor, no red and no notification. VS Code no longer reminds you with “Still waiting”, and an agent of the call’s own session that waits for you is told in one red line instead of two.
• A click takes you where you can answer. A click on what needs you (the red line, the status line, the visitor, the question card, the VS Code and desktop notifications) opens that session in Claude Code: its tab, in the VS Code, Cursor or Windsurf window that runs it, whether the call is in the editor, a browser or the desktop app. A session in Terminal, iTerm2 or the Claude app brings that app to the front (macOS). With several windows of an editor that does not have the Agent Standup extension, that editor comes to the front and you pick the tab. The first time, VS Code may ask whether Claude Code can open the link. G still only moves from one to the next. The call goes to the session too, as before. Nothing is sent anywhere: a local link is opened, as a click on it would.
• See the browser an agent drives. When an agent drives Chrome (Claude in Chrome) or the Claude desktop app’s own browser, the call’s shared screen becomes a browser window: the page’s title and address, its last screenshot, a pointer that glides to each click, what it types, and the agent’s own words for each step.
• Told when a new version is out, if you want. The desktop app, the command line and the Claude Code plugin ask once whether to tell you. Off until you say yes; then at most one request a day to the npm registry for the number of the latest version, nothing about you or your sessions, never with DO_NOT_TRACK or NO_UPDATE_NOTIFIER set. The notice shows how to update that app: download it again, the two plugin commands, or the npx or npm command to copy. The command in the README and on the website is now npx @double_geste/agent-standup@latest --open, which always starts the latest version.
• Claude Code 2.1.300 to 2.1.302. A lead waiting on sub-agents that run in the background is no longer “your turn”, a fork joins the call as the lead’s twin and its tokens count once, and the recap shows the cost Claude Code counted and each agent’s effort and advisor.
• A line above the Claude Code prompt when another session needs you. A second plugin, agent-standup-band, shows which other session waits on a question or an approval, and a short toast when one starts waiting or finishes its turn, in the terminal and in the Claude desktop app’s Code tab (Claude Code 2.1.294 or later): /plugin install agent-standup-band --marketplace Atoll92/agent-standup.
• Easier to find in VS Code. The extension is now listed as “Agent Standup: Claude Code & Codex Agent Monitor”, and the README opens with install buttons for VS Code, Cursor and the macOS app.
• French: “vous attend ?” instead of “attend vous ?”.