Novi Notes 1.1 - A local AI memory layer for your Mac

@ferdi_sigona Thanks for raising this — it's something I've been thinking about a lot, so let me give you the honest answer.

iOS isn't on the roadmap right now, mostly because of depth over breadth. I'm using the Mac app every day for my own work, and there's still a long list of rough edges I want to address before splitting focus across platforms. Sync is the other half of it — I actually shipped iCloud Sync early on and ended up removing it entirely, because any real fix means putting a server or account system between your devices, which is the exact thing Novi exists to avoid. So instead I've leaned toward markdown export + your-own-git-repo as the portability story. That seems to fit the way you already work, keeping CLAUDE.md right next to the code.

That said, what you described — "I'm in transit and I want to dump a thought into the memory layer" — is a narrower problem than full iOS parity, and probably the more interesting one. A write-only quick capture (Drafts-style: open app, type, it lands in today's Daily Note or an Inbox) is a much smaller sync surface and keeps the Mac as the source of truth. If iOS ever happens, it'll almost certainly look like that rather than a port.

Thanks for the framing — that depth/breadth lens is exactly how I think about it too.

@naimz Honestly: I haven't built a dedicated team-sharing solution. It's local-first by design —

no Novi account or server in the middle — so there's no "share with your team" feature as

such.

What the current setup lets you do is lean on the fact that a skill is just a plain file:

- "Export to File…" writes it out as a standard SKILL.md that you can hand to a teammate to

import on their end.

- Project-scoped skills live in your repo's .claude/skills/, so if you already share that

repo, committing them means teammates pull via git and Refresh Skills picks them up.

But to be clear, those are general file/git workflows, not something I built specifically

for teams — and they're a copy, not a live link, so once imported each person manages their

own. A purpose-built sharing flow isn't there today; it's a fair gap to flag.

@bhuvika_mehta 
Thanks — that "deploy from one place" bit is exactly the itch I was trying to scratch.

On versioning: there's no built-in revision history today. Editing a skill updates it in

place, and re-deploying overwrites the SKILL.md in each target you've pushed to (Claude

Code, Codex, Gemini) — so the previous version isn't snapshotted automatically. The upside

is that a deployed skill is just a plain SKILL.md file, so if you want history you can keep

it under git, which works especially well for project-scoped skills in your repo's

.claude/skills. A built-in version history isn't there yet — I'll note it as a request.

On discovery: the MCP server is scoped to your notes and documents, so it doesn't expose a

"list all skills" tool — and it doesn't need to. Skills deploy as native SKILL.md files into

each agent's own skills directory (e.g. ~/.claude/skills/), so Claude Code / Codex / Gemini

pick them up and list them through their own native skill loading. The agent already sees

what's available without a separate call.

The other direction is covered by a Refresh Skills button: it re-scans the on-disk skill

directories and reconciles them with Novi's list — importing skills that were added outside

Novi, detecting edits via a SHA-256 fingerprint, and flagging files that went missing or

conflict across roots (it marks them, never deletes). So Novi stays honest about what's

actually deployed, even for skills it didn't create.