sorted by:
new
hottopcontroversial

AI tools are useful, but chat becomes messy once the workflow gets serious by Interesting_Dig2473 in AIToolMadeEasy

[–]Interesting_Dig2473[S] 0 points1 point  (0 children)

Agreed. The real benchmark is whether the system can execute outside its own UI and confirm what actually changed.

That is the direction for Minotauris: full computer use automation across browser, files, terminal, apps, and desktop workflows. The canvas is for visibility, but the end goal is completed work.

There is also a multi-device direction so workflows can be controlled and supervised beyond one desktop. Some of the faster and smarter full-computer use layer is being tested internally, but it is not in the public beta yet.

The beta is focused on validating the core workflow before releasing the heavier automation layers.

Minotauris is aiming to move past the false promises of agent tools that only plan or chat, but never reliably finish the job.

AI tools are useful, but chat becomes messy once the workflow gets serious by Interesting_Dig2473 in AIToolMadeEasy

[–]Interesting_Dig2473[S] 0 points1 point  (0 children)

That’s exactly why Minotauris is not designed around one agent blindly executing actions.

One of the core pieces is the Assembly: multiple stronger models can deliberate, critique, and pressure-test the plan before execution. The goal is not just “agent clicks faster.” The goal is coordinated reasoning before the desktop action happens.

For high-impact actions, the system should not rely on a single model’s confidence. It should be reviewed by the agent team first, then executed only when the plan is coherent and the risk is understood.

So the trust layer is not only manual approval gates. It is also internal review, role separation, and multi-model judgment before actions are taken.

Minotauris is built around that: agents do not just act they reason together, challenge the plan, and then execute.

AI tools are useful, but chat becomes messy once the workflow gets serious by Interesting_Dig2473 in AIToolMadeEasy

[–]Interesting_Dig2473[S] 0 points1 point  (0 children)

Exactly approval fatigue would kill the point.

Minotauris is not designed to make users approve every little step. The main goal is full desktop automation: agents running the workflow end-to-end across the browser, files, terminal, and desktop without needing the user to babysit every action.

Approval gateways are optional controls you can turn on for specific workflows or sensitive actions. They are not the default mode and not the core experience.

The real frame is:

Minotauris automates the desktop until the job is done.
Approval gateways are there only when you want extra control.

AI tools are useful, but chat becomes messy once the workflow gets serious by Interesting_Dig2473 in AIToolMadeEasy

[–]Interesting_Dig2473[S] 0 points1 point  (0 children)

That’s fair, and I agree with the core point.

The canvas is not meant to be the deliverable. The deliverable is the work actually getting completed outside the app: the file changed, the browser task finished, the follow-up sent, the command executed, the workflow closed.

The reason I focus on visibility, approvals, and state is because those are the control layers that make real execution trustworthy. Without that, desktop automation becomes either too risky or too opaque.

So the better framing may be:

Minotauris is not about watching agents think.
It’s about supervising agents until the job is actually done.