I built something I've wanted for a while within an hour using Claude Code (Sonnet 4.5).
It's a LLM conversations viewer, available for everyone to use at https://tomzxcode.github.io/llm-conversations-viewer.
It is a single page application, 100% client-side.
You can use it to view conversations exported from various LLM platforms (e.g., ChatGPT, Claude, etc.) in a nice interface.
It can also be used to share conversations with others so that they can view them, using https://tomzxcode.github.io/llm-conversations-viewer/?url=url-to-json-or-zip (such as a raw Gist URL).
It can be useful if you use many platforms through their clients (web or mobile) and would like to be able to search those conversations in one place.
Play with it and let me know what you think!
Repository here
The lab called it the Repository.
Time was not a river. It was a commit graph.
Mara’s console showed history as hashes and arrows. Every moment a node. Every decision a branch. The past was immutable. The future was a working tree full of untracked files.
She did not travel backward. She checked out.
git checkout -b stop-war a1f3c9e
The world recompiled around her. Same initial state. Same variables. Different branch name. In this timeline Hitler was still a student. Mara changed one small file. A rejected application. She committed and returned.
git checkout main
Nothing changed. Of course not. Main was untouched. The war still existed. The scars still matched their hashes.
People kept asking why she could not fix history. She explained patiently. You never fix history. You fork it.
Each jump created divergence. Entropy grew like unmerged branches. The Repository ballooned. Infinite timelines. Infinite storage. Garbage collection impossible. Nothing was truly unused.
One day she found a branch tagged by someone else.
origin/hope
No author. No timestamp. The diff was small. Fewer deaths. Slower weapons. More pauses between commits.
Mara did not merge it. Merges caused conflicts. Merges caused paradoxes.
She rebased.
She replayed the present onto hope. One commit at a time. Carefully resolving conflicts. Choosing better defaults.
When she finished, the graph looked cleaner. Still complex. Still branching. But survivable.
She pushed.
Somewhere, someone typed their first commit message.
“Initial commit.”
Dr. Sarah Chen stared at her terminal, the familiar green text glowing in the darkened lab.
$ git log --all --graph --oneline
* a3f9b2c (HEAD -> main) Fix climate models
| * 7c8d1e4 (origin/2157) Prevent asteroid impact
|/
* 2b4a8f3 Initial timeline"Three timelines," she muttered. "And they're diverging."
The Temporal Version Control System had seemed like humanity's salvation. Jump to any point in history, create a branch, make changes, then merge back. Fix mistakes. Optimize outcomes. What could go wrong?
Everything, apparently.
Sarah's colleague Marcus rushed in. "We've got a problem. The 2157 branch where we prevented the asteroid? It created a merge conflict with main."
"Show me."
$ git merge origin/2157
Auto-merging timeline.dat
CONFLICT (content): Merge conflict in timeline.dat
Automatic merge failed; fix conflicts and then commit the result.Sarah pulled up the diff:
<<<<<<< HEAD
2089: Global climate stabilized, population 9.2B
2157: Thriving lunar colonies established
=======
2089: Asteroid prevention tech drives new space race
2157: Mars terraforming 40% complete, population 12.7B
>>>>>>> origin/2157"They're both real," Marcus whispered. "Both timelines exist simultaneously until we resolve the conflict."
Sarah nodded slowly. Quantum superposition at a temporal scale. The universe itself refusing to compile until they chose which future to keep-and which to discard.
Her fingers hovered over the keyboard. One timeline solved climate change through sacrifice and discipline. The other achieved it through desperate innovation sparked by near-extinction.
"What if," she said, "we don't choose?"
"You can't leave a merge conflict unresolved. The timeline will remain in an unstable state-"
"Or we git rebase everything onto a new branch. Cherry-pick the best commits from each timeline."
Marcus's eyes widened. "You want to rewrite history itself."
"We already are. We've just been doing it badly." Sarah started typing:
$ git checkout -b unified
$ git cherry-pick 7c8d1e4 # Asteroid prevention tech
$ git cherry-pick a3f9b2c # Climate stabilityThe lab hummed. Reality flickered.
When the command completed, Sarah checked the log:
* e9f2a1b (HEAD -> unified) Climate models + prevention tech
* 2b4a8f3 Initial timelineClean. Linear. Optimal.
"Git push --force?" Marcus asked nervously.
Sarah smiled. "Git push --force."
She hit enter.
The universe accepted the merge.
Every daily at the end of the (work) day.
5 minutes.
- Determine what are the most important tasks to be done tomorrow (manual)
- Determine the next step for each task (manual)
- Determine how much work can reasonably be accomplished tomorrow (manual)
Every week at the beginning of the (work) week.
10 minutes.
- Determine what are the most important tasks to be done this week (manual)
- Determine the next step for each task (manual)
- Determine how much work can reasonably be accomplished this week (manual)