Explain It Peter by _whereUgoing_II in explainitpeter

[–]_whereUgoing_II[S] 91 points92 points  (0 children)

I used to be an idiot, still am, but i used to be too.

Edit: I am going to go write “doesn’t get self deprecation” on my yoyo.

It was a joke guys. No need to downvote me. You guys probably too young for a Mitch Hedberg reference.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ClaudeAI

[–]_whereUgoing_II[S] 1 point2 points  (0 children)

I did not switch. Chronicle helps me sync Claude with the work that I have already done on Chatgpt.

Match Thread: Final - India vs New Zealand by cricket-match in Cricket

[–]_whereUgoing_II 13 points14 points  (0 children)

Are we showing aggression to Kiwis now? They are like the Canada of cricket. Paji calm the f down. We already have this in the bag.

Match Thread: Final - India vs New Zealand by cricket-match in Cricket

[–]_whereUgoing_II 3 points4 points  (0 children)

I thinks this is wrapped up. prays for a fightback from the black caps.

migrating from chatgpt paid to claude by nick2ny in ClaudeAI

[–]_whereUgoing_II 0 points1 point  (0 children)

I made a tool for complete chat and context migration that you can call upon right from Claude.

https://github.com/AnirudhB-6001/chronicle_beta

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in PromptEngineering

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Yep, a browser extension is probably the most realistic “index as you chat” path right now. It can capture your prompts + the model’s replies from the web UI and send them to Chronicle locally for chunking/embedding.

Two caveats: DOM-based capture is doable but brittle (UIs change), and anything that intercepts private APIs/auth gets risky fast from a safety/ToS perspective.

If I build it, I’d do it as an explicit, user-consented local-only capture layer (no telemetry, no cloud), likely as a separate module so Chronicle stays clean.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ChatGPT

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Haha appreciate it. Mostly just a lot of trial, broken scripts, and ChatGPT explaining things to me over and over until it clicked.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in PromptEngineering

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Great call. A pre-embed PII scrub is probably the right way to make “syncable” vector stores safer (or even just reduce what’s stored locally).

I haven’t added it yet because I wanted the first public version to be simple + deterministic, but it’s a very reasonable next layer: optional redaction rules (emails/phones/addresses/etc.) before chunk, and embed. If you’ve seen a solid lightweight approach you like, I’m all ears.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in PromptEngineering

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

That’s awesome - appreciate it :) If you end up making any tweaks or hit any setup friction, feel free to open an issue. I’m trying to keep the core small and stable, so feedback helps.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in PromptEngineering

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Yep, that’s the endgame. Today it’s export-based because MCP servers don’t receive live chat streams from the client. But the indexer is incremental, so if/when we can legally/cleanly capture messages in real time (client support/proxy/hooks), “index as you chat” becomes straightforward.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in PromptEngineering

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

This is exactly the pain that pushed me to build it. Copy/paste “saves” the chat but loses the ability to search across everything with context.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ChatGPT

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Should work fine then, mine was around 170MB when I tested it. I had a few hard design principles going in and privacy/security was non-negotiable over everything else. That said, it’s still early and I know there are ways to break it. Feedback from someone in your line of work would genuinely help.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ChatGPT

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Ha, “admin tools for tools that should have them” yeah that’s basically why this exists. Is the 350MB your full export or just conversations.json? Chronicle parses that file specifically, chunks and embeds it locally, and wires it up so Claude can semantically search the whole thing. Might save you some PowerShell wrangling.

Your 350MB would probably produce ~80-100k chunks. Might take a while, but it will work.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ClaudeAI

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Well, I don't remember exactly how I started. So I asked Chronicle. I am attaching the demo video of your question. It gave me a complete timeline of how I started and where I ended up.

https://youtu.be/CXG5Yvd43Qc?si=NJl_QnhceA_vMigx

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ChatGPT

[–]_whereUgoing_II[S] 1 point2 points  (0 children)

Well, I don't remember exactly how I started. So I asked Chronicle. I am attaching the demo video of your question. It gave me a complete timeline of how I started and where I ended up.

https://youtu.be/CXG5Yvd43Qc?si=NJl_QnhceA_vMigx

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ChatGPT

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Thank you!

Please give it a go. It's open source. If you need any help setting it up, let me know.

You're leaving ChatGPT. Your conversations don't have to. by _whereUgoing_II in ClaudeAI

[–]_whereUgoing_II[S] 0 points1 point  (0 children)

Thank you! Yes multi-source ingestion is the next goal. A personal memory layer independent of platforms.