Thanks! We fixed some of the videos now.

That makes a lot of sense when reading, but in reality a lot of things have snapped back to plain text over and over again.

I don't know the exact reason for that, but it's undeniable that it happened.

Lots of people try completely new novel GUI stuff all the time, always from basic principles. Looks clean and neat but doesn't survive the real world. Meanwhile, plain text tools have been improving and spreading roots consistently for decades.

Could be that a GUI gets some showtime, but wouldn't bet against plain text at any time. It's like betting against spoons.

Yeah, we speak in words, so I'm not saying text would go away entirely. Even in our Marble interface, you can still type follow-up prompts to a task. But plaintext won't be an interface by itself.

One thing I mentioned before is that the representation of artifacts produced by AI being inspectable has notable value.

I miss this in some existing agentic interfaces. I'm not typing into the text editor, I'm inspecting the work it does. Not exactly "reading every line", but definitely inspecting.

I understand not all kinds of works can be like this, and having to understand how "a bunch of text files" become something else (a program, or a page, or etc) is really taxing on cognition (that's why GUIs exist), but also really beneficial for verification (you can see the guts of the thing).

So, it's not prose text. I'm talking about the artifact produced by the agent having a plain text representation.

Lacking that produces back-and-forth interactions that feel exhausting. I can make Claude design a spreasheet for me, and it will present it beautifully for me, with export to Google Sheets and so on. But then, changes to it don't let me dig up into it interactively. I need to open the spreadsheet externally, then translate my attempt at debugging the issue to the chat back, which is super slow.

Designing one inspectable interface for each kind of produced artifact/outcome sounds like a lot of work. And plain text solves this beautifully (it is an interface) by introducing formats (like Markdown for documents).

I'm not suggesting every single AI user will eventually migrate to IDEs with sidebars, but I think something closer to it will be prominent for a foreseeable future in major important work done with AI assistance (the kinds of things that really matter, big work).

Some of your demos are not opening, so I don't know what is the MarbleOS solution for things like spreadsheets or more elaborate artifacts that, today, in tools like Claude, produce this exhausting back-and-forth I mentioned.

Also, I must say the exhausting part is really only exhausting for power users (the guy that does a lot of spreadsheets needs the speed, not the ease of use). For beginners, a more guided approach might be best. For something that carries the OS terminology, I would expect both approaches to be present at some capacity (other harnesses fail at this too, so don't worry).

We think that humans will remain in charge for quite some time. Even a superintelligence won't know what we want until we tell it. The process of communicating intent/desires etc to an AI agent is a nontrivial interface problem (which Marble is trying to get at).

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.

I think being able to view it as a graph would make things much faster. Because choosing to use AI means you're taking on work that exceeds your own cognitive limits.

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