r/GoodOpenSource • • 1d ago

Markbase is open source: one markdown folder for your team and its AI agents

/r/Markbase/comments/1xycohb/markbase_is_open_source_one_markdown_folder_for/
0 Upvotes

2 comments sorted by

•

u/AutoModerator 1d ago

Please post a comment here explaining what kind of contributions you, or the project you are posting about, are looking for. For example what skill sets, any rules important for people joining in your build like how often people should post, and anything else you can think of which will help readers decide if they want to join in and start coding with that project.

Thank you and be excellent to each other. u/roamingandy

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Snoo31321 1d ago

The stack: TypeScript throughout, in an npm workspaces monorepo:

  • a Next.js web app

  • an Electron Mac app

  • a Node CLI that does the folder sync

  • Yjs CRDTs for merging

  • Supabase/Postgres for storage and auth

Where help would matter most

  • Windows and Linux desktop builds (Electron): the Mac app is Apple silicon only today.

  • Self-hosting without Supabase: running on plain Postgres plus a simple auth option would make self-hosting much easier (Postgres, auth, Docker).

  • Conflict handling: when the same lines change on two machines and can’t merge, the cloud’s text currently wins and the local copy goes to a .conflicts folder. A better review or merge flow would be great (CRDTs, editor UX).

  • Agent integrations: skills and instructions so Codex, Cursor, Gemini and others read and write the vault well, not just Claude Code.

  • On-call templates: incident doc, runbook and postmortem templates for teams that let agents do the first pass on incidents. SRE experience is welcome even if you don’t write much code.

  • Bug reports and feedback: if you try it with your team or your agents, tell us what breaks. That’s as valuable as code.

How to join in

  • Open an issue before a big change so we can agree on the approach. Small fixes can go straight to a PR.

  • Contributions are Apache-2.0. Sign off your commits with git commit -s (DCO); there’s no CLA. Details are in CONTRIBUTING.md.

  • There’s no required cadence: drop in whenever you have time. I review PRs and answer issues myself.

  • Questions and ideas are welcome in r/Markbase or as GitHub issues.

Repo: https://github.com/Markbase-Team/Markbase