docs.dev vs Meeting Notes Sync

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

Sync meeting transcripts, notes, and AI summaries from MacParakeet and Fellow into your vault.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About Meeting Notes Sync

Sync meeting transcripts, notes, and AI summaries from MacParakeet and Fellow into your vault. Each artifact is tagged by source ( Summary (MacParakeet).md, Summary (Fellow).md ), so a meeting captured by both stays unambiguous. The index carries both source ids and the meeting interval; uncertain matches are flagged merge-confidence: low for review. The vault is your archive, deleting a meeting in a source never touches your vault, and files you add to a meeting folder are left alone.