​
Clear Comet Cache for Langflow

guide2026-06-034 min read

When Langflow looks stale inside Comet, clear the browser’s site data first, then restart Langflow only if the UI still reflects old state.

langflowcometbrowser-cache

​
Summary

If Langflow behaves as if an old flow, component, or UI bundle is still loaded in Comet, treat the problem in layers. Start by clearing Comet’s site data for the exact Langflow origin, then hard-refresh the page, and only then move on to restarting Langflow or clearing local Python caches.

​
What This Solves

This guide solves the common case where Langflow appears stale in Comet: the page still shows old UI state, old flow metadata, or behavior from before a local restart. The successful outcome is a clean Langflow page load without unnecessarily clearing unrelated browser data or touching project files.

​
Who This Is For

This is for someone running Langflow locally or through a remote URL and opening it in Comet. It assumes you can access the Langflow page and can restart the Langflow process if browser-side cleanup is not enough.

​
Prerequisites

  • Access to the Langflow page in Comet.
  • The exact URL you use for Langflow, such as http://localhost:7860 or http://127.0.0.1:7860.
  • Terminal access if you need to restart the Langflow server.

​
The Workflow

1

Identify the exact Langflow origin

Check the address bar before clearing anything. localhost, 127.0.0.1, a LAN IP, and a public domain are separate browser origins, so Comet may cache each one independently.
2

Clear site data for only that Langflow origin

In Comet, open the page’s site settings from the address bar, then clear cookies and site data for the Langflow URL. This should remove cached localStorage, cookies, and browser-side state without affecting every site you use.
3

Hard-refresh the Langflow page

Reload the page with Cmd + Shift + R. This forces Comet to re-fetch the app shell and assets instead of reusing a cached page load.
4

Repeat for alternate local URLs if needed

If you sometimes open both http://localhost:7860 and http://127.0.0.1:7860, clear site data for both. Browsers intentionally isolate these origins.
5

Restart Langflow only if the browser cleanup fails

Stop the running Langflow process and start it again. Use the command that matches how you normally run it.
pkill -f langflow
uv run langflow run
If you do not use uv, start it directly:
langflow run
6

Escalate to Python cache cleanup for custom code

If the stale behavior comes from custom components or local Python code, inspect Python cache folders before deleting anything.
find . -name "__pycache__" -type d
Start with Comet’s per-site cache and a hard refresh. This keeps the fix targeted and avoids wiping unrelated browser sessions.

​
Common Failure Modes

Clearing only localhost will not clear 127.0.0.1. If you switch between both URLs, stale state can survive because each URL has its own site storage.
Restarting Langflow will not always fix stale browser assets. If Comet is serving an old app shell, the server can be fresh while the page still behaves as if it is old.
Avoid clearing global Comet profile data as the first step. It can remove unrelated cookies and sessions, while the Langflow problem usually only needs per-site cleanup.

​
Final Checklist

  • Confirm the Langflow URL you are actually using.
  • Clear Comet site data for that exact origin.
  • Run a hard refresh with Cmd + Shift + R.
  • If using both localhost and 127.0.0.1, clear both.
  • Restart Langflow only after browser cleanup fails.
  • Inspect Python cache folders only if custom components or code changes still do not load.

​
What To Remember

Treat Langflow cache problems in layers. Browser origin state is the first layer, Langflow process state is the second, and Python/package cache is the last layer. Most Comet-specific stale UI issues are fixed before reaching the last layer.

​
Metadata

Quick Reference

Typeguide
Statuspublished
Date2026-06-03

Retrieval Tags

langflowcometbrowser-cachetroubleshooting
Related
LangFlow SystemsBrowser Cache Debugging