Tine
v0.1.0 June 24, 2026 · original r/logseq thread ↗

Tine — drop-in faster Logseq OG replacement

The first release. Here's what I wrote when I announced it — unedited.

Hi! I vibecoded Tine, a drop-in Logseq OG replacement mainly built to be faster, but also with some features I missed.

The why: I loved using Logseq, but at some point realized I can't use queries because they are slow / make logseq use a lot of CPU even when idle (yeah weird). Then every summer my laptop starts overheating and it is partially because of the electron apps. When CPU throttles, the apps get slow. Surely there must be a way to do this faster.

The what:

  • I first just wanted logseq, but faster. I don't use whiteboards, flashcards etc., so these are currently unavailable. I focused on features that I use.
  • It just works over your OG graph — reads and writes the same files. It should be safe and compatible but it was only ever tested by one person, on one platform, one graph, so be warned. (On the other hand yes, I am actually using this on my real graph worth 5 years of life, and I'm syncthing-ing it to my Android phone and there editing it using the logseq app, and nothing has broken yet.) Also, there are automatic backups.
  • I added some features that I liked — some I knew from OG plugins (tabs), some just seemed like a (really) nice thing to have: tabs, focus+dim mode, quick-capture, carry tasks to today, etc. Look at the readme.

AI: full disclosure, everything except this text is completely vibecoded, including the README.

Let me know what you think / any ideas for changes / features etc. If you find bugs, let me know via github issues. This is still beta at best, so bugs are expected.

📦 v0.1.0 release & changelog ↗ 💬 Full discussion on r/logseq ↗

From the discussion

The thread ran from delight to well-earned skepticism. A few exchanges I keep thinking about — Claude tries to summarize the others faithfully and generously; the originals are linked, so you can check; my own are quoted in full.

“You're not even a developer?”

secretBuffetHero

Desperate for a Logseq replacement. He'd considered vibe-coding one himself but was sure it would take too long, and is genuinely curious how much effort this took. He's relieved I picked “a normal language” instead of Clojure — and slips in a wishlist item: more standard Markdown (he was never thrilled Logseq spun its own flavor).

Me OP

I'm just a user, but AI coding is currently good enough for the task I needed, so I let AI code it up for me. (I'm currently building up the release on github, so it should be available in the next few hours after I iron out the kinks.)

My goal was not a replacement - I think the design is fantastic - just a version which works quickly (and does a few more things).

secretBuffetHero

Floored: you're not even a developer, and you built a clone in a few weeks? “The world is freaking insane now.”

Me OP

A week and a half. It does not have feature-parity, just all the features I ever needed. But yes, the world is insane (and more is coming). It was built with Opus 4.8 + Claude Code but I'm pretty sure other SotA models would be able to do it too (GPT-5.5 for instance). Claude is just the most comfortable to work with right now.

Would you trust a vibe-coded app with your data?

micalm

Wouldn't ever trust a vibed app with his data — but calls it the best LLM-use disclosure he's seen so far, and wishes me luck.

Me OP

Hehe. I understand. But things are changing fast with LLMs; if you are coming from an experience 6 months back, claude code / codex are a pretty different experience (part because the harnesses got better, mainly because the models got vastly better).

runs11trails

Wonders whether being open source makes Tine — vibe-coded or not — actually more trustworthy than Logseq.

micalm

Both are open source, he answers — but that in itself means nothing until someone actually audits the code, and he doesn't have the time. If Tine grows enough that someone qualified takes a look (or he gets a chance to try it in a safe environment), he will. He's not writing it off just for being vibe-coded.

The honest state of the stack

pereira_alex

On Linux the AppImage crashed under Wayland (EGL_BAD_PARAMETER); he found an LD_PRELOAD workaround. He warns that Tauri/WebKitGTK on Linux is “a very bad story” next to Windows and Mac — and pushes back on my framing: Electron is not a reason Logseq is slow. With Tauri you'll always hit “the CSS rule that doesn't quite work on all platforms”; with Electron everything is the same everywhere. Still — great work, and great dedication to scratch your own itch.

Me OP

Hi - just to say you were right - I hit some scrolling bug which turns out to essentially be "webkitgtk is crap". It is kind of minor, but annoying. Hopefully nothing more serious will come up.

Me OP

Yes - I think you're right that a smaller change was necessary (instead of clojure + datascript just have the rust backend + chromium frontend); but I'm not a software engineer, don't understand the stack, so I just went with what Claude proposed. Oh well, it's not terrible.

How to read this: comments by other people are Claude's summaries — it tries to be faithful and generous — and the originals are linked on Reddit, so you can check; my own replies are quoted verbatim. Usernames link to their Reddit profiles.