[BUG] Dev servers started by Claude are hard to find and outlive the app

Status Open
Maintainer reply None cached
Activity 1 comment · opened Oct 6, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

A Code-tab session started a Vite dev server (vite --port 5173 --strictPort) with the preview tool. After the turn ended, the session showed as idle, but the server kept running. The only way to find it was ⋮ → Processes inside that one session. Nothing in the sidebar or session list showed that a server was still running. Running processes should be visible at a glance.

Quitting the Claude desktop app didn't stop the server. It stayed bound to port 5173 with no way to see it in the UI. Child processes like this should be shut down when the app quits, or at least flagged.

What Should Happen?

Running processes should be visible at a glance.. Child processes should be shut down when the app quits, or at least flagged.

Error Messages/Logs

Steps to Reproduce

This is a UI always-existing bug, it isn't triggered by running code as far as I can tell.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.19675.1

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗