How to remove a stale local dev backend from the dashboard?

[vale oracle]

I have a "Local Backend" entry stuck in my project dashboard (shows "Masushi's MBP - Port 3210") but I don't have any npx convex dev process running. It's been there for a while and won't go away on its own.

Is there a way to manually disconnect/remove it from the dashboard? Or does it eventually time out?

[random saffron]

Hi @vale oracle. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

The knowledge sources don’t describe how “Local Backend” entries are created/removed in the dashboard, nor any explicit timeout or manual “disconnect” control for them. I can’t say for sure how long they persist or exactly when they disappear.

What is documented:

• Local backends started by npx convex dev run as a subprocess and “exit when that command is stopped”; their state is stored under ~/.convex/. [Local deployments]
• Local deployments are treated as development deployments attached to a project and are visible in the dashboard, but there’s no mention of a UI to delete a specific local backend entry. [Local deployments; Deployments]

Given that:

• There’s no documented way in the dashboard to manually remove a single local backend entry without affecting the whole project.
• There’s no documented timeout/TTL for a stale local backend entry.
• Local backend state lives in ~/.convex/, but the docs don’t specify which files to edit/remove to clear a single stale entry, so I can’t safely recommend a specific file operation.

If the stale entry is only cosmetic and not blocking you, the safest option (based on the docs) is to leave it; it should not affect your cloud dev or prod deployments. If it’s causing real issues, the best next step is to ask in the Convex Discord so the team can either clean it up on their side or advise on a supported workaround, since this behavior isn’t covered in the current documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: