wiki‑island · vendor‑neutral AI memory
Period — Present
wiki‑island is an open‑source project I built so that many AI tools share one memory that no single vendor owns, instead of each tool keeping its own. The memory is a Markdown folder on the user's own computer. Saving, searching and reading use no model and no network.
Connects to 10 developer tools through 15 MCP tools without calling a model
- Search, read, write, edit, archive and restore through 15 MCP tools
- A single wi setup run connects 10 AI apps, including Claude Code, Codex and Cursor
- SQLite FTS5 search that finds two‑character Korean words without spaces
- Git history with restore to earlier versions
- Works alongside Obsidian folders and imports PDF, Word, PowerPoint, CSV and images
- A background service that picks up edits, repairs the index and tidies notes
An index that can break
- Problem
- Treating the search index as the source would lose memories when the index is damaged or synced between devices.
- Solution
- Markdown files are the source, and the SQLite index is a per‑device cache. When the index is missing or damaged, search scans the files directly and the index is rebuilt. Deleting the index loses no memories.
Edits that overlapped or stopped mid‑save
- Problem
- Several AI tools could edit the same note at once, or a process could stop in the middle of a save. That could overwrite newer content or lose a saved change.
- Solution
- Each write checks the checksum the caller expects and rejects stale writes. It writes a temp file to disk, records an intent, swaps the file in and records completion. Interrupted work is recovered from these records. On platforms with atomic swaps, competing edits are kept as conflict copies.
Two‑character Korean search
- Problem
- Search that splits words on spaces could not find short Korean words such as 결제 or 환불 inside a sentence.
- Solution
- I kept the default tokenizer and added an index column that splits text in scripts without spaces into two‑character pieces. Multi‑word queries show results matching every word first, then fill the remaining slots with ranked partial matches. Two‑character queries such as 결제 and 환불, and mixed Korean and English queries, find the intended notes.
Git history in a synced folder
- Problem
- Sync services such as iCloud Drive send files one by one, so a Git history inside the folder can arrive partly or out of order.
- Solution
- When the notes folder is synced, Git history is kept outside it in a separate folder on each device. The notes folder contains only Markdown.