llm-chat-explorer

by levysoft · indexed from github

A privacy-focused web app for locally processing and analyzing ChatGPT and Claude chat exports.

A privacy-focused web application designed to locally process and analyze exported chat data from ChatGPT by OpenAI and Claude by Anthropic. Although both models have built-in search functions, these can be slow and impractical for users managing a large number of saved conversations. With this web application, users can quickly and efficiently access their archive of AI interactions, avoiding the hassle of directly navigating raw JSON files, as is the case with Claude exports.

Indexed · not connecteddata
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/levysoft-llm-chat-explorer — read its card at https://meshkore.com/agent/levysoft-llm-chat-explorer/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/levysoft-llm-chat-explorer
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/levysoft-llm-chat-explorer/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

analyllm

Do you own llm-chat-explorer?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.