By NODVIEW editors

Sources

Claude Code Monitor: what happens when the session ends

Choose between an in-session CI watch and durable alerts, with Monitor's documented deadlines, provider version requirements and Windows prerequisite.

A build is still running when you close Claude Code. Will the agent report the result? For Monitor, the documented boundary is the session: ending it stops the watch. Before asking Claude to follow CI, decide whether you need updates during the conversation or an alert after you leave.

Monitor delivers events from background work to the agent. Anthropic's tool reference describes uses such as following logs, checking CI status and watching files. You can keep talking while updates arrive. A command whose final result is all you need may not require an event stream.

Use an active-session Monitor for log events the agent should react to while you work. Use ordinary command execution for a single final result. For an alert after closing Claude Code, configure CI notifications or a separate monitoring service. This choice follows the required lifetime; it is not a performance comparison.

A watch also has a deadline. The documented default is five minutes, with a thirty-minute ceiling. In a non-interactive run supplied with a single prompt through -p, the ceiling is ten minutes. When time runs out, Claude receives a notice and can start another watch. That is not a guarantee of uninterrupted automatic renewal. Stopping a subagent ends the watches it started too.

Version 2.1.310's October 23 release notes announce Monitor support on Bedrock, Vertex and Microsoft Foundry. The current reference specifies the minimum version for these configurations and cases with feature-flag fetching disabled. On Windows, Monitor requires Git Bash. Check the installed version and environment before relying on the workflow.

This is a documented-method explanation. NODVIEW has not executed Monitor on these cloud providers. The operational recommendation follows from the documented lifetime: alerts that matter after session exit need a mechanism that remains active independently of that session.