Comments URL: https://news.ycombinator.com/item?id=49621223

Points: 60

# Comments: 32

We just want to make sure we're grounded in real-world practical utility because it's easy for ambitious interface ideas to remain demos. We have a lot more exciting, weird, and strange ideas to come!

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.

We see this playing a role in things like tool selection, ie setting up shortcuts similar to gaming macros for quick selections.

For a lot of tasks, I don’t think you will need to stay inside the document or app the whole time. But I can also imagine starting from an asset you already have open ie a PDF, spreadsheet, etc and bringing agents and tools into that context, rather than creating a separate task and attaching the asset again.

With that in mind, I agree that fanning out into disconnected task outputs is not enough. Sometimes the asset itself should become the center of the workspace, with the delegated work happening around it.

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)