HTML as the default LLM output format changes what you want from a file manager. The "web of HTML files" Thariq describes is what TagSpaces was built to browse — HTML and MD preview inline, S3 mounts alongside local folders, tags work across both.
@trq212 Strongly agree on HTML. On the S3 step: a file manager mounting S3 natively keeps "draft local, publish via S3" in one tree. I use TagSpaces — HTML/MD preview inline whether local or in the bucket. Tagging at generation time also pre-solves your find/group/categorize step.
@karpathy This is essentially the workflow I've been converging on — the missing piece being where these files live. I use TagSpaces over the folder: it previews HTML inline (like a browser tab) and renders Markdown the same way. No upload step. MD and HTML side-by-side, tags span both.
"Claude Code + Obsidian is the most powerful AI combo I've ever used." — @aiedge_That tweet brought the recipe to PKM Twitter. @karpathy posted his version, Noah Vincent wrote 5K words on it, @shmidtqq followed up. I lived in the recipe for months. Then I noticed what's missing↓
The recommendation isn't "switch tools."
Both apps read plain files from the same folder.
Obsidian for writing the wiki. TagSpaces for the raw layer — PDFs, emails, web clips — and visual perspectives across every file type.
Use both. They share the same room.
TagSpaces version 5.1 is out, including a shiny new perspective allowing you to present any folder from your hard drive as a Kanban board. Beside this we added some new UI themes, improved the file creation dialog and added a history navigation.
https://t.co/zSmVcx3uqL
Last week, we released version 5 of TagSpaces including tons of new features and improvements like:
* A free and open source web version
* Connecting S3 buckets now free feature
* A lot way to customize your folders
* ...
You can find out more in our blog:
https://t.co/hjb0lUyqU1