Launched this week
Sheeep
Git-native workspace for docs, planning, and code memory
6 followers
Git-native workspace for docs, planning, and code memory
6 followers
Sheeep is a Git-native workspace for teams that want docs and planning to live with code, but accessible everywhere. Store pages asshp and boards asfrm in your repo. Features a premium Notion-style editor in VS Code and a full web workspace (with PWA) for collaborators. Open PDF, DOCX, and XLSX files natively. It’s the ultimate way to collaborate on project memory without context switching, and far more efficient for agents than separate MCP connections. Replace Notion with your repo.
SCode Studio
Hey Product Hunt! 👋
I'm Jaseunda, the creator of Sheeep.
Documentation and planning shouldn't be trapped in a browser tab while you're working in your editor. We spend our lives in VS Code, yet our projects' 'brains' the plans, the roadmaps, the architecture notes are often buried in proprietary clouds or disconnected wikis.
I built Sheeep to solve this 'context switch' problem for my own team. In fact, this is exactly what we use inside Voyveray to manage our entire operation. Every doc, every Kanban board, and every asset in our repository is managed through the .shp and .frm files you see today. We found it so transformative for our workflow keeping our memory local, Git-native, and instantly accessible to our AI agents that we decided to polish it up and share it with the world for free.
It's a full-platform workspace. Whether you're a developer in VS Code or a non-technical collaborator using our web version (or PWA), you're all working on the same files in your Git tree.
Key highlights:
1. Git-Native Memory: Documents (.shp) and Boards (.frm) are real files in your repository.
2. Works Everywhere (Offline!): A dedicated editor for VS Code, plus an offline-ready app for iOS, Android, and Desktop.
3. Used Internally & Shared for Free: This is our own secret sauce for productivity at Voyveray, now available to everyone.
4. Collaboration for All: VS Code for devs, easy-to-use web workspace for everyone else.
5. Agent Ready: Stop juggling MCP connections give your agents direct, native access to your project's brain.
6. Universal Viewer: PDF, XLSX, and DOCX inside the same workflow.
7. I'm here all day to hear your thoughts and feedback. Happy documentation! 🐑
SCode Studio
'Why not just use raw Markdown instead of `.shp` files?'
It's a great question! Here is why we made that choice:
1. Collaboration for Everyone: Raw Markdown can be intimidating for non-technical team members. Sheeep provides a 'Notion-like' rich experience that feels premium and easy to use. Just like they’re used to in Notion, non-technical teams can access everything via the web workspace.
2. Unified Project Memory: Instead of exhausting yourself with back-to-back MCP connections or fragmented docs, Sheeep keeps everything in one place. Whether it's a doc, a board, or an asset, it’s all in your repository.
3. AI Agent Optimized: While agents can read Markdown, the structured nature of Sheeep's document model makes it much easier for AI to navigate, edit, and understand the hierarchy of your project. It gives your agents a single, high-fidelity 'brain' to interact with.
Cool concept - the idea of keeping docs and planning inside the repo instead of jumping between Notion, Confluence, and VS Code is something I've been wanting for a while. Context switching between your code and your project docs is one of those silent productivity killers that nobody talks about enough. The fact that non-technical team members can still access everything through the web workspace is a nice touch too - that's usually where Git-native solutions break down. Curious about one thing - how does conflict resolution work when a dev edits a .shp file in VS Code at the same time a PM updates it through the web app? Does it handle merges gracefully or can things get messy?
SCode Studio
@ben_gend Thanks, really appreciate this.
Today, conflict handling is Git-native rather than “live collaborative” (no OT/CRDT layer yet).
If a .shp file is edited in two places at once, Sheeep treats it like normal Git concurrency:
web edits are committed against a known base
if that base is stale (someone already pushed changes), the write is rejected instead of silently overwriting
you then refresh/rebase to latest and re-apply the change (or open a PR path)
So yes, it can get messy in true simultaneous edits, but we fail safe (no hidden data loss).
We’re exploring a friendlier conflict UX next (diff/merge assistant for .shp/.frm), while keeping the source of truth in Git.