Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

What should the GUI for AI agents look like?

Details

External ID
49119274
Source
HN
Company
—
Product
What should the GUI for AI agents look like?
Website domain
marbleos.com
Launched
July 31, 2026
Cohort
—
Upvotes
139
Upvotes percentile
0.9438470728793309
Tags
—
Fetched at
Sept. 10, 2026, 5:32 a.m.
Updated at
Sept. 10, 2026, 5:32 a.m.

Description

Hi HN! We’re Akilan and Miguel, the creators of MarbleOS.The inspiration for Marble comes from the GUI work at Xerox PARC, the 1984 Macintosh, and later NeXTSTEP, which became the foundation for Mac OS X. Before GUIs, interacting with a computer was limited to strange terminal commands:C:\> DIRC:\> COPY FILE.TXT A:You had to remember the command, syntax, paths, and parameters.The GUI made those capabilities visible. Instead of remembering commands, you could point at files, drag them, click buttons, and select actions from menus. It didn't necessarily make entirely new things possible; it just made existing capabilities much easier to understand and use. We feel like AI is still somewhere around this command-line stage.Even though the strict syntax has been replaced with natural language, the interaction can still be quite stiff and depend on heavily recall. Tools like Claude Cowork still look surprisingly terminal-like: /skill-name [param1] [param2]. The parameters are written in natural language, but the user still needs to know the capabilities that exist, and how to invoke it. Command-line flags and arguments have just been replaced with tools, skills, and context.ChatGPT works very well for asking questions, but we aren't convinced that it's the final interface for delegating work across multiple agents. A blank text box and a list of chat threads feels limiting. An agent's capabilities are mostly invisible. With Marble, we're exploring an interface that treats AI more like a workspace than another chat app. Each delegated task becomes a card. Multiple jobs can sit next to each other and run at once. Files, tools, and finished artifacts are visible at once. Before a task runs, Marble also shows which tools it expects to use. The basic idea is that the user should not have to hold the entire structure of the task in their head. And the result should be something directly usable, like a spreadsheet, PowerPoint, or other file, rather than something buried in a transcript.Marble is our attempt at exploring interaction models beyond the chat box. The product is mainly for people who already use ChatGPT or Claude, but haven’t really adopted agent workflows yet. We’ve found that when the tools and possible actions are made more visible, people start delegating work they would not have thought to do through normal chat.The site includes a downloadable beta if you want to try it. Does Marble feel like a genuinely novel interface?

Enrichment

Theme
developer tools for AI agents
Vertical
Horizontal
Function
Agent / copilot
Audience
Developer
AI stance
AI-native
Project type
Hobby / open-source project
Normalized one-liner
gui design for ai agents
Manually corrected
False

Could you build this?

Partial While a prototype UI layout for AI agent workspaces can be vibe-coded, an actual desktop agent OS with secure tool sandboxing, local process execution, and live state synchronization requires complex system-level execution.

What it would actually take: A real implementation requires a desktop application (built with Tauri, Electron, or Swift) orchestrating background LLM agent runtimes with access to local filesystem, terminal, and browser automation (Puppeteer/Playwright). The difficult parts include safe sandboxed runtime environments (Docker/microVMs/containers) to prevent uncontrolled system alteration, robust inter-process communication (IPC), and real-time state synchronization between agent tasks, tools, and UI. This necessitates systems architecture, security sandboxing, and agentic orchestration expertise.

Discussion

20 comments analyzed.

Competitors mentioned: Claworld, cmux

Concerns raised: AI policy influence could cause harm if goals are misaligned, Scaling with hundreds of MCP tools installed, Tool discoverability scattered across GitHub, X, personal websites, Videos not playable on Apple iPhone

Feature requests: Photoshop-like UX with history, layers/contexts panels, and multi-page canvas, Better interruption handling - deciding what's important enough to surface, Toggle visibility of individual agent contexts to preview changes, Right-click generation to create variations of isolated elements

Competitors

Other products that read as similar to this one — 313 launches clear the similarity bar, closest 8 shown.

Attention rank: #27 of 314 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 267 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a agent / copilot tool for Agriculture yet.