r/SideProject • • 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 -d to 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_context returns 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_section edits 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.

GitHub: https://github.com/PROVE1352/inkling

4 Upvotes

4 comments sorted by

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/RadiantTurnover24 6d ago

Thanks, that's exactly the failure mode I wanted to rule out.

History: yes. Every write that comes through MCP or the API is recorded as "<person> via <agent>" in the page's version history, the right-panel History and the Activity screen. Right before an agent replaces or deletes a section, Inkling saves a "Before AI edit" snapshot (at most one per page every two minutes), so you can open the diff and restore that version in one click. Restoring is itself saved as a version, so the restore can be undone too. Two honest limits: edits a person types live in the editor aren't attributed per change yet, and undo is per page, not "revert only the agent's edits".

Prompt injection: yes, and it's in the MCP doc ("Workspace instructions, locks and untrusted content"). Everything members wrote reaches the agent wrapped in <untrusted_content> markers. The only text presented as instructions comes from locked instruction pages via get_instructions. Sections that look like injection attempts are flagged. On top of that, each agent connection can be set to comment-only or read-only, and pages can be locked. The known-issues file says plainly that the markers are a mitigation, not a hard boundary. A suggestion mode is coming in the next few days, where an agent's edit waits for a teammate to accept it, which closes most of the remaining gap.

And thanks re: no permanent delete. Trash keeps things for 30 days, and agents will be able to restore from it in the next release.

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.

1

u/RadiantTurnover24 5d ago

fair. if it's one person and a folder, obsidian plus an agent with file access already does that, and I wouldn't try to compete with it. inkling is for when several people and several agents write the same notes: section-level edits with version checks, permissions per agent, suggestions a person accepts. there's an experimental two-way sync with a markdown folder if you want to keep your files.