11–20 of 98 posts
Why are you assuming that the human is in charge? Needing a human to drive the AI is probably a transitional phase.
Why are you assuming that the human is in charge? Needing a human to drive the AI is probably a transitional phase.
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 yo…
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 cognitive overhead in day to day tasks (both in specifying what you want, and managing after you ran something)
I don't think we should homage GUI for AI agent workflows. The terminal and Mac GUI are 100% deterministic when you click an icon, but I'm not sure if visualizing agent workflows is the right call. The problem is that AI workflows are inherently different for each person. The current approach feels like it's forcing a CLI-based model on users. I also don't think chat is a suitable fundamental unit for task delegation…
Totally agreed that chat interfaces won’t be sufficient to enforce complicated gates. Our interface does have the concept of a workspace, where you can see all the cards at-a-glance within the workspace. But graphs, or otherwise finding a way to have the tasks interact with each other, could be an interesting direction.
For small tasks, you don't need AI. You can produce high-quality code just fine on your own. I can maintain very high quality for codebases up to about 40,000 lines. But using AI means you're trying to handle complexity at the scale of 100,000, 200,000, or even 300,000 lines, complexity that an individual can't fully digest. That requires an additional interface, and I believe that interface should be graph-based.
I agree with your view. I like this product quite a bit, but for controlling AI, I think it's still at the prototype stage
Why are you assuming that the human is in charge? Needing a human to drive the AI is probably a transitional phase.
However, I believe the GUI for AI agents that will win is a plain text editor with a file tree, a terminal pane for coding (or preview pane for other kinds of tasks) and a chat sidebar.
Even if the code editor is not used to type, it's there for psychological safety. It lets you inspect and navigate what is being created. Has tremendous value.
Plain text has survived countless software revolutions, so it's likely to become the dominant format for artifacts produced by AI. Non-plain text things are likely to adapt instead of the other way around.
"Strange terminal commands" have survived, while even poweruser toolbar style have started to fade (I love them, but they're fading away). It clearly has some value (hint: speed over familiarity).
I think the poweruser toolbar style was indeed the only thing in the past couple of decades that really tried to match the terminal for speed of interaction. In my opinion, it succeeded, but it has its limits too (tends to clump with stuff over time; has a limit on the amount of abstractions it can hold). I would love to see a candidate GUI that tackles that speed angle.
It does feel novel. However, I believe the GUI for AI agents that will win is a plain text editor with a file tree, a terminal pane for coding (or preview pane for other kinds of tasks) and a chat sidebar. Even if the code editor is not used to type, it's there for psychological safety. It lets you inspect and navigate what is being created. Has tremendous value. Plain text has survived countless software revolutions…
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 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…
It's similar to needing aol to get online in the 90s/00s. Eventually this will become built in and become invisible in a sense.
I'm glad someone is working on this because it's been annoying having to sacrifice process to gain capability.