Shipped Khayal v1.1.2
- Better semantic search (chunk-level)
- Proactive connections after capture
- Entity extraction
- Optional AI answers over your vault
Still fully local + plain markdown.
https://t.co/sbN5VU9Hlv
@theo Its not just specs that cost you its the maintenance burden the company has to incur that shoots the price up, and if you believe hetzner is costly try other services you will love herzner
You asked for roast here you go(no pun intended),
- It doesn't matter what you do or how good the site is, the idea of delaying the user input as simple as a mouse move is a weak start
- The fact that you chose a humongous Nextjs framework for a simple portfolio site makes me think of a midwit meme
- I bet you didn't see your pagespeed scores
mine: https://t.co/ZYRwZUWqxe
Your prompt was never the thing the model was worried about, it was the code and context it had, model calls are stateless the relevant things get transferred on every calls, keep those things thin and your problem is solved, use plan mode to plan and compact the session and then build
@JiaYongLim1008@Nazik2053 If the vault is plain markdown, you’re not locked into Claude, Kimi, or anyone else.
Capture and retrieval can sit on top of the same files.
At this point, you are not even locked to an editor
@Nazik2053 This is the key point.
This is the last thing that should quietly leave the building by default.
Local files + local processing should be the starting assumption, not an afterthought.
@KanikaBK Local markdown files for the win.
That’s the whole point. Own the files, stay offline-capable, and never get locked into someone else’s format.
@cyrilXBT The problem was never Obsidian + Claude.
You don’t even need Obsidian to make this work.
Obsidian is mostly a capture + retrieval layer - the real system is the files, the workflow, and how you get thoughts in.
Solve ingestion and you’re already halfway to a better result.