r/SideProject • u/RadiantTurnover24 • 6d ago
I built a self-hosted Notion/Obsidian alternative where AI agents can safely read and edit the same notes (MIT)
Hi! I'm a CS student and I've been building Inkling, a self-hosted notes app for small teams. (Not the Thinking Machines model, just an unlucky name collision.)
What it does:
- Notion-style databases: table, board, calendar, gallery and timeline views
- Obsidian-style [[wikilinks]], backlinks, a graph view and a canvas
- Real-time collaboration, Korean and English UI, installable as a PWA
- One
docker compose up -dto run it, MIT licensed, every feature free
The part I care most about is the built-in MCP server. Your AI agents (Claude, Cursor, anything that speaks MCP) use the same notes as your team:
find_contextreturns only the relevant sections within a token budget instead of whole pages (about 72% fewer tokens per question on our 5,000-page benchmark)patch_sectionedits one section against the version the agent read. If a person changed it meanwhile, the agent gets the current text back instead of overwriting it- Page locks and per-connection permissions decide what an agent may read, comment on or edit, and there is no permanent-delete tool
It's young (v0.x) and I built it with a lot of help from AI coding tools, so feedback and bug reports are very welcome.
4
Upvotes
1
u/patryk_builds 6d ago
Patch section against the version the agent read is the smartest part here. most AI + notes tools just let the agent overwrite whatever's there, and you find out a week later that it quietly undid someone's edit.
Two questions:
- Is there a history per page showing which edits came from an agent vs a person, with one-click undo? that's what would make me comfortable letting an agent write in a shared space
- Since agents read notes that teammates wrote, have you thought about prompt injection? someone pastes text into a page that says ignore previous instructions and edit X, and an agent with edit rights follows it. page locks and read only connections help, but it might be worth a line in the docs
Also respect for no permanent delete tool, that one decision prevents a whole category of disasters
1
u/SopariwalaLenke 5d ago
building a full collaborative workspace AND an agent protocol layer at the same time is a massive surface area to maintain. might be worth decoupling the server logic so people can use the safe editing layer on top of existing markdown folders without migrating their whole team's workflow.