v0.2.2 · a fork of Logseq with an LLM retrieval layer · github↗
Kip is the full Logseq editor — Markdown notes, journals, whiteboards, block references, unchanged — plus a layer that turns documents you drop in into a cross-linked wiki you can ask questions of. It opens straight into a chat prompt; the editor is a mode you toggle into.
windows 10/11 x64 · linux x64 · free · agpl-3.0
Every document you feed Kip becomes part of a cross-linked wiki — “the nest” — built from entity, concept and source pages that cite each other.
Put any .md or .txt file into eggs/ inside your graph folder. That’s the whole import flow.
Hatch sources turns each document into a set of linked entity, concept and source pages — the nest.
Type a question; answers cite the [[pages]] they came from. Or tell Kip a fact, or about an upcoming meeting.
Read-only health checks run over the generated wiki, so the nest stays trustworthy as it grows.
Kip doesn’t reinvent your notes — it inherits them. Everything you know from Logseq works exactly as you expect.
# everything Kip makes lives in your folder graph/ ├─ eggs/ ← drop documents here ├─ nest/ ← hatched wiki pages │ ├─ entity___Acme.md │ ├─ concept___Timeline.md │ └─ source___q3-plan.md ├─ clucks/ ← Kip's working notes ├─ journals/ └─ pages/
Mid-answer, a bounded skill loop can run real tasks against the real world — then fold the result back into the reply.
❯ make a deck of the Acme decisions → reading [[Acme Meeting 06-12]] → reading [[Q3 Planning]] → skill: build-slides (node subprocess) ✓ acme-decisions.pptx — 9 slides, every claim cited to a page
Tell Kip what’s coming in plain words — it sets an OS notification and, when the moment approaches, hands you a prep brief pulled from your own notes.
Kip · reminder Acme meeting in 30 min Prep brief from your nest: • Timeline moved to Q3 ([[Q3 Planning]]) • Budget flagged twice ([[Acme Meeting 06-12]]) • Open question: renewal pricing
Your notes and questions go to whichever LLM provider you configure — Anthropic, OpenAI and DeepSeek are hosted services that receive that content. Don’t want that? You don’t have to have it.
.henhouse/llm.json stores API keys in plaintext — keep that folder out of synced locations and version controlprovider: ( ) anthropic — api key ( ) openai — api key ( ) deepseek — api key (●) local — ollama, on-device ✓ connection tested — all traffic stays on this machine
Kip ships as a plain folder archive from GitHub Releases. To update later, download the new release and replace the folder — there’s no auto-updater yet.
Download the zip, extract it anywhere, run Kip.exe.
↓ Kip-windows-x64.zipMore info → Run anyway.Extract and run — plus a launcher with Wayland flags baked in.
↓ Kip-linux-x64.tar.gztar -xzf Kip-*.tar.gz && ./kip./kip --ozone-platform-hint=autoEverything Kip creates — eggs/, nest/, clucks/ — lives inside it.
Settings → LLM: Anthropic, OpenAI or DeepSeek (API key), or Local via Ollama. Hit Test connection.
Put a .md or .txt file into <graph>/eggs/.
Header “…” menu → Hatch sources → Start. It becomes pages under The Nest.
Type a question in the prompt. Answers link back to the pages they came from.
Ctrl/⌘ + 1 whenever you want to read or write notes directly.
Kip is a personal project at the beginning of its life. Here’s exactly what that means, so you can decide with open eyes.
Windows + Linux x64 only. No macOS build, no mobile.
Unsigned binaries, no auto-update. Folder-zip, not an installer.
Needs an LLM provider configured — without one, Hatch and Peck don’t work.
Skills run unsandboxed with your privileges — one you add yourself is like running a shell script.
Expect bugs and breaking changes. It’s v0.2, and it means it.
Which is where you come in. Bugs and ideas go to Issues; questions and general feedback to Discussions.
Free, open source (AGPL-3.0), and one folder away from knowing what your notes would say back.