Hey Product Hunt
I'm Justin, the maker of Liminal, and I'm stoked to finally share what I've been building!
Heads up: this is the first cut. I'm launching now to find out if the friction I've been feeling is real for other people too. All feedback is welcome, and please let me know if you run into any bugs or problems, I'll get them fix asap!
Quick backstory
Last summer, the way I work changed. Agents got good enough to become the place I did the work. Claude Code became my main interface, the intelligence layer everything flowed through. My job shifted from writing and producing to directing an agent to do it.
Notion and Google Docs weren't built for this. They were bolting agents into their apps, but that's not where my agent lived, and their MCPs were slow and expensive to talk to. Claude Code worked much better and faster with local markdown files, a format the agent already speaks. So I stopped writing in Notion and Google Docs and went all in on local markdown.
I was doing all of this in VS Code because that's where I coded. But viewing and editing markdown there is clunky. You use the preview to render it nicely, then jump to the raw side to actually edit. So I built a WYSIWYG editor on top of the local files.
Then I tried to share something. Nobody wants to be sent a raw markdown file, and Google Drive doesn't render it nicely. Passing files back and forth killed any hope of collaboration. So I built real-time live collaboration on top of local files: a lightweight CLI watches your workspace folder and syncs bidirectionally with the cloud. Share a link and your teammate opens the same live workspace in a browser. Their edits land back on your disk instantly.
Once that worked, the thing I hadn't designed for showed up. My agent and my teammates' agents were all reading and writing into the same workspace. Liminal had quietly become a shared second brain. Company knowledge that keeps updating and compounding as the team works, sitting on every agent's local disk as plain files they can directly access.
What Liminal is
A collaborative workspace for humans, agents, and teams. Your AI-native second brain. Bring your own agents. Own your files.
How it works:
Work with your agent, not just through it. Your agent writes files to disk in markdown or HTML. Liminal renders them as clean UI the moment they save. Review and edit naturally in the browser, without wrestling with raw markdown.
Share instantly, without the friction. A lightweight CLI syncs your workspace to the cloud in real time. Send a link and your teammate is in the same live workspace. No sending markdown over Slack, no hosting your own HTML, no waiting on Google Drive.
A shared second brain for every agent on the team. Files live locally, so every agent has direct access to everything the team has written, decided, and learned. No external calls, no lag, no losing context between sessions.
No middleman, no MCP tax. Direct file access means no MCP round-trips, no proprietary formats, no wasted tokens. Context is cheap, fast, and always fresh.
The ask
Would love your feedback, especially if you're living in Claude Code, Codex, or another agent all day: does this map to your experience, or am I solving a problem only I have?
Justin
https://useliminal.xyz
Liminal
Hey Product Hunt 👋
I'm Justin, the maker of Liminal, and I'm stoked to finally share what I've been building!
Heads up: this is the first cut. I'm launching now to find out if the friction I've been feeling is real for other people too. Please let me know if you run into any bugs or problems, I'll get them fix asap!
Quick backstory
Last summer, the way I work changed. Agents got good enough to become the place I did the work. Claude Code became my main interface, the intelligence layer everything flowed through. My job shifted from writing and producing to directing an agent to do it.
Notion and Google Docs weren't built for this. They were bolting agents into their apps, but that's not where my agent lived, and their MCPs were slow and expensive to talk to. Claude Code worked much better and faster with local markdown files, a format the agent already speaks. So I stopped writing in Notion and Google Docs and went all in on local markdown.
I was doing all of this in VS Code because that's where I coded. But viewing and editing markdown there is clunky. You use the preview to render it nicely, then jump to the raw side to actually edit. So I built a WYSIWYG editor on top of the local files.
Then I tried to share something. Nobody wants to be sent a raw markdown file, and Google Drive doesn't render it nicely. Passing files back and forth killed any hope of collaboration. So I built real-time live collaboration on top of local files: a lightweight CLI watches your workspace folder and syncs bidirectionally with the cloud. Share a link and your teammate opens the same live workspace in a browser. Their edits land back on your disk instantly.
Once that worked, the thing I hadn't designed for showed up. My agent and my teammates' agents were all reading and writing into the same workspace. Liminal had quietly become a shared second brain. Company knowledge that keeps updating and compounding as the team works, sitting on every agent's local disk as plain files they can directly access.
What Liminal is
A collaborative workspace for humans, agents, and teams. Your AI-native second brain. Bring your own agents. Own your files.
How it works:
🟢 Work with your agent, not just through it. Your agent writes files to disk in markdown or HTML. Liminal renders them as clean UI the moment they save. Review and edit naturally in the browser, without wrestling with raw markdown.
🟢 Share instantly, without the friction. A lightweight CLI syncs your workspace to the cloud in real time. Send a link and your teammate is in the same live workspace. No sending markdown over Slack, no hosting your own HTML, no waiting on Google Drive.
🟢 A shared second brain for every agent on the team. Files live locally, so every agent has direct access to everything the team has written, decided, and learned. No external calls, no lag, no losing context between sessions.
🟢 No middleman, no MCP tax. Direct file access means no MCP round-trips, no proprietary formats, no wasted tokens. Context is cheap, fast, and always fresh.
The ask
Would love your feedback, especially if you're living in Claude Code, Codex, or another agent all day: does this map to your experience, or am I solving a problem only I have?
Justin
You asked whether this maps to people living in Claude Code all day, and from my desk the answer is yes, the friction is real. My whole setup runs on a folder of markdown memory files with an index loaded each session, and it quietly became the most durable part of my workflow because notes survive every context reset. The failure mode I keep hitting is staleness, a note written three weeks ago names a file or a flag that no longer exists and the agent recommends it confidently anyway. Does Liminal do anything to age or flag entries when the thing a note points to changes, or is pruning still on the human?
Liminal
@abdullah_javaid3 Right now Liminal has no opinions about your data and files, it's just a workspace that makes collaboration between humans, agents, and teams easy and accessible, but I can see a future where it does more than that!
this is one of those launches where the backstory tracks exactly with my own workflow - i ended up doing the same VS-Code-preview-then-raw-edit dance before giving up and just living in Claude Code with a folder of notes. the part i'm most curious about is scale rather than sync: once a team's second brain grows to a few hundred files across months of work, how do you actually find the right one? plain markdown in folders works great at 20 files and turns into its own kind of clutter at 500 - is there real search/structure on top, or is it still mostly relying on the agent to know where to look?
Liminal
@omri_ben_shoham1 It turns out that LLMs are amazing at search already, and giving agents the ability to just grep your entire workspace is pretty effective even when you have hundreds or thousands of files! So today Liminal has no separate search capabilities and I believe that AI model companies will build better search faster than I can
@justinonthelam The concurrent write answer above covers editing at the same time, but I'm curious about the offline case: if you're working locally with the sync CLI not running, say on a flight, does everything just work as plain markdown with nothing lost?
Liminal
@justinonthelam good to know!. Since conflict resolution is UI-based today, does reconnecting after a long stretch offline surface one clean diff to work through, or could it come back as several scattered conflicts across files if a teammate's agent was also writing during that window?
Liminal
@clement_avq today it's a diff per file but the idea of having a single diff (or experience to manage all diffs) would be cool. Thank you for the idea!
@justinonthelam Glad it's useful! If you build a combined view, I'd want it to group by file first and flag when two diffs touch the same section, that's probably the case that actually needs a person's attention versus five independent one-liners!
Liminal
the "everyone with the link sees the same live workspace" part is the piece I'd want to understand before using this for real team work - once an agent is writing files into a shared space, it's going to write things that were meant for one person's eyes at some point (a draft perf note, a client's rough numbers, whatever). is there any per-file or per-folder permission layer, or is the model still "anyone with the link sees everything," just like the underlying markdown files would if you handed someone the folder
Liminal
@galdayan 100%! Liminal is built with per file access controls, just like Notion or Google Docs. Users can have their own personal workspaces, or limit access to files in a shared workspace!
@justinonthelam good to know, that answers the main worry. follow-up: is the default on a new file private-to-me until I explicitly share it, or does it inherit the permissions of whatever folder/workspace it gets created in? asking because if an agent is the one creating files, it needs to make that call itself in the moment, and "default to private" vs "default to the folder it's in" changes how careful you'd need to be about telling it where to save things
Liminal
@justinonthelam good, private-to-me by default is the safer answer. one more since you said folder inheritance is coming: once that ships, will it stay additive on top of private-by-default, or will dropping a file into an already-shared folder start overriding the file's own default? that distinction matters a lot for an agent, since it decides whether "save this here" can silently widen who sees something.
'work with your agent, not just through it' is the real reframe. when two agents write the same file at once, does it merge or last-write-win?
Liminal
Love the local-first approach, feels way less wasteful than passing markdown around. One thing that would seal it for me: a small sidebar showing who is currently editing which block, so we can avoid stepping on each other during live sessions.
Liminal