Feature request: remote session monitoring from Claude mobile app / claude.ai

Resolved 💬 3 comments Opened Apr 7, 2026 by RobinMaddicott Closed Apr 11, 2026

Summary

I'd love the ability to monitor and interact with running Claude Code sessions remotely — from the Claude iOS app or claude.ai — without needing SSH or a terminal app on my phone.

Use case

I frequently kick off long, multi-step agentic tasks in Claude Code on my laptop and then step away. Right now, if Claude needs input (tool approval, a clarifying question, etc.), it just blocks until I'm back at my desk. Being able to check in from my phone would be a huge quality-of-life improvement.

What would be useful (rough priority order)

  1. Read-only live log — stream the conversation output to a linked claude.ai or mobile session so I can see progress
  2. Push notification on completion or block — "Your session finished" or "Claude is waiting for input" would cover 80% of the value
  3. Remote interaction — approve/deny tool use, answer questions, or send follow-up messages from the mobile app
  4. Session list — see all active Claude Code sessions linked to my account, with status (running / waiting / done)

Possible implementation directions

  • WebSocket-based session sync — Claude Code CLI opens a WS connection to a relay; claude.ai/mobile subscribes to the same session ID
  • Build on MCP — an MCP server that exposes the session log as a resource and tool approvals as callable tools
  • Lightweight alternative — even a simple webhook/push notification on session completion or tool-approval-needed events would be valuable

Context

I run Claude Code on Windows 11 with multiple long-running background agents (scheduled tasks, pipeline runs, etc.). The existing --background and remote agent features are great — this would complement them by closing the "monitoring gap" when I'm away from my desk.

Thanks for considering this! Happy to help test or provide more detail.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗