MarbleOS - A GUI for AI Agents with visible files and tools
Show HN: What should the GUI for AI agents look like?
MarbleOS reimagines the interface for AI agents by moving beyond restrictive chat threads. This innovative workspace presents files, tools, tasks, and outputs in a clear, visible layout, empowering users to manage complex AI workflows with precision. Instead of burying critical data in conversation history, MarbleOS offers a structured environment where every element is accessible and actionable. Users can experience this new paradigm through the live demo or by downloading the beta version to transform how they interact with autonomous agents.
A workspace with visible files, tools, tasks, and outputs — not buried in chat threads.
- tdeck
I'm glad folks are experimenting with different paradigms.
That said, Hacker News might not be the best audience for this informal survey. I'd wager at least 70% of the people reading this are still interacting with their computers using "strange terminal commands", by choice. We aren't representative of what normal people will use or prefer.
- enriquto
> Before GUIs, interacting with a computer was limited to strange terminal commands [...] Even though the strict syntax has been replaced with natural language
This post, and particularly the two quoted sentences, has activated anger pathways in my brain that I didn't know existed... An extremely visceral, primary, response. I find it unbelievably jarring to read.
- qsort
I completely agree with you that the chat interface is very undercooked and there's a big untapped space for agent-first interfaces, perhaps even replacing traditional desktop metaphors. You're spot on with your premise.
With that said, from the material you show in your homepage, it still seems like you're doing something very similar to OpenAI and Anthropic's first party apps?
I think it would help your pitch if you could show some task or workflow where your interface truly makes a difference; loading files and asking questions about them is a staple of most harnesses.
- visarga
Best interface in my opinion is a git tracked folder, files as state, agents coming in and doing work. It's not just a chat interface because in chat mode everything flows like water under the bridge. It is files as agents, where you get the agent to write a task in a file, and then it updates the file like a blackboard as it performs work. Same task file can be seen by worker agent, multiple judge agents (for plan and implementation), documentation agents and reflexion agents (improve workflow). I would also track every user message in a chat_log.md for reflexion agents (what is wrong with the workflow) and intent review (is the agent still following user intent?).
- ilaksh
I think there is going to be an intersection between a personal operational dashboard like this and the UI for an AI Company.
I've been predicting for awhile that 2026 is the year of the AI Employee (or serious attempts) and 2027 is AI Companies.
I have been seeing RFPs recently asking for end-to-end solutions to operate companies in particular industries with the goal of day-to-day only requiring infrequent human-in-the-loop.
Anyway, if you think about what for example some professionals might use a Marble like tool for, say managing their freelance business. You might want to create a task and then promote it to be scheduled and then have that artifact like a report have a dedicated place on the screen.
The difference with a vertical is that you will know a lot of the reports and data types you need ahead of time. The advantage with just prompting things dynamically as you go is you get exactly what you need and don't have to sort through a bunch of features that aren't important to you.
Even though a business vertical is qualitatively different, you still might use the same system to build it. Maybe something like a self organizing AirTable. A set of projects as departments.
Sorry I started rambling nevermind.