I think my outlook client might be the most ideal interface once we get some of the rough edges sorted out.
Show HN: What should the GUI for AI agents look like?
71–80 of 98 posts
Re: Show HN: What should the GUI for AI agents look like?
#72theoretically this is interesting, but in practice it's just one layer that sits atop what is ultimately still many individual chat boxes. Did you try anything else, anything a little more novel?
Another idea was a "preview" step before running a task, which used dummy data to mock up a visual of what the output from a task could look like. This allowed you to shape the structure of the task results before even running it. It ended up being confusing as it was hard to tell real vs fake/simulated dummy results.
Something we will be keeping, though, is the ability to have an artifact opened i.e., a spreadsheet, Slides, PDF... and select or interact with any part of the document, and Marble proactively suggests ways to extend that document with the context of what you selected/highlighted, and the purpose of the workspace/the work task. It will look like a tool selection wheel used in video games.
Re: Show HN: What should the GUI for AI agents look like?
#73Re: Show HN: What should the GUI for AI agents look like?
#74I 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 yo…
I think a better example is how Marble makes tools visible and easy to select for each task instead of requiring you to remember what exists or describing everything through the prompt. Marble keeps the tools you use most close at hand and will surface other useful ones for the job. Combined with a birds eye view of multiple tasks running, it makes agent work easier to set up and manage. The goal is to minimize cogni…
Re: Show HN: What should the GUI for AI agents look like?
#75I 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 yo…
I just want a clean way to manage chats, projects, and research. I mean I know I can pin so many chats, and I can group things in projects. But I am doing a brand design project with nearly 30 - 40 chats in one project at the moment, and the fact that you can't rename a chat from within a chat (or even see the autogenerated name for that point). You can't tag or apply any logical grouping to chats in a project i.e. L…
Re: Show HN: What should the GUI for AI agents look like?
#76Best 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 a…
Re: Show HN: What should the GUI for AI agents look like?
#77Re: Show HN: What should the GUI for AI agents look like?
#78Re: Show HN: What should the GUI for AI agents look like?
#79I think the GUI for AI agents should simply be a slot machine. Pull the handle.
Re: Show HN: What should the GUI for AI agents look like?
#80I think it should look like this: https://www.dreamcoder.ai/ A smart, tiling window manager with workspaces and a great tool harness. An everything app, if you may; bring the terminals, code reviews, etc. into the tool itself, and make it high fidelity: no blocky terminals for the app itself.
Don't see the need for a special UI.