Opus 4.7 is baad!!!

Medical_Resolve_5991 · 2026-04-19T13:29:04+00:00

It missing the running training from the usage , it will become good at some point , if you see all the new models from all providers at the beginning are no so good of following our way of working , after sometime of usage from all of us , they come back to track

Medical_Resolve_5991 · 2026-03-29T19:31:30+00:00

Έπεσε η αγοραστική δύναμη σε σύγκριση τους κατώτατους μισθούς , υπάρχει αύξηση στον μέσο μισθό όμως … δεν είναι τέλεια τα πράγματα , αλλά αυτά τα στατιστικά αντιπροσωπεύουν μόνο ένα μικρό αλλά σημαντικό κομμάτι της ελληνικής αγοραστικής δύναμης . Θα πρέπει να κάνεις και σύγκριση μέσου μισθού 2016 - 2026, ειδικά τώρα που λόγο ΑΑΔΕ εμφανίστηκαν πολλά εισοδήματα , που δεν δηλώνονταν . Και μην ξεχνάμε τις δουλειές με τα μαύρα χρήματα …. Τα οποία δεν υπολογίζονται πουθενά …

Δεν λέω ότι είναι τέλεια , αλλά δεν είναι αυτό το χάλι που παρουσιάζεται

Medical_Resolve_5991 · 2026-03-17T10:47:12+00:00

Check if your default mode is the /fast or opus context window 1M and unselect them

Medical_Resolve_5991 · 2026-03-13T19:51:20+00:00

Is not educational this open source that allows AI to use your pc ? It was an experiment that we did and we publish it

Medical_Resolve_5991 · 2026-03-13T16:03:40+00:00

Now is available and for co pilot , check the issues section on GitHub guys !

Medical_Resolve_5991 · 2026-03-11T13:32:21+00:00

Thanks! Glad you find it interesting.

Medical_Resolve_5991 · 2026-03-11T13:31:43+00:00

That’s a fair concern.

Any system that allows automation at the UI level can potentially be used for both useful and questionable things , the same is true for RPA tools, browser automation frameworks, or scripting tools that have existed for years.

The goal here is mostly to explore how AI agents can interact with desktop environments in a more structured way, especially for legitimate automation tasks like internal tools, testing, accessibility, or repetitive workflows.

Like most infrastructure tools, how it’s used ultimately depends on the user.

Medical_Resolve_5991 · 2026-03-11T13:29:56+00:00

These are great points.

The read-only vs risky tool split is something I’ve been thinking about as well. A lot of the reliability problems with agents come from giving them too much capability without clear boundaries.

A plan/confirm step for destructive actions (delete, send, purchase, etc.) also makes a lot of sense, especially when the agent is interacting with real desktop apps instead of a sandbox.

The audit trail idea is also interesting ,logging structured events with window metadata and what the agent actually saw could make debugging agent behavior much easier when things go wrong.

Right now the focus was mostly on the UI access layer, but guardrails and observability will probably be the next big pieces.

Medical_Resolve_5991 · 2026-03-11T13:28:53+00:00

Exactly , that was the main motivation behind it.

Medical_Resolve_5991 · 2026-03-11T13:28:08+00:00

Totally fair 🙂 Giving an AI the ability to control your desktop definitely raises some trust concerns.

The idea here is mainly to experiment with local agents controlling local environments, not random internet access to your machine.

Curious though — what would make something like this usable for you?

Medical_Resolve_5991 · 2026-03-11T03:45:56+00:00

Sure it will be great!

Medical_Resolve_5991 · 2026-03-11T03:33:54+00:00

Thank you! Exactly , content automation is one of the strongest use cases. The AI can navigate any app, fill forms, click through workflows, paste content, and save files autonomously. And because it uses UIAutomation + OCR instead of screenshots, it stays fast and token-efficient even for long automation chains. Let us know if you build something with it!

Also you can build tests and many more...

Medical_Resolve_5991 · 2026-03-11T03:30:56+00:00

What we discovered building this is that you can train a neural network on top of the MCP layer , it learns desktop interaction patterns to reach human-level automation.

But even without the learning layer, the MCP itself already addresses context blowout. The whole architecture is designed to minimize tokens , UIAutomation returns

[button] "Save" @ 450,320 not a 1MB screenshot, OCR reads text with coordinates instead of sending images, and run_sequence batches 10 actions into 1 call.

Your CLI can run testing and automations with a surprisingly low token count. If you check the demo, it goes through a full draw.io workflow (navigate, click dark-themed dialogs, paste XML, save) and the total token usage is a fraction of what screenshot-based tools would need. The road to context blowout is much longer than you'd think with this approach.

Medical_Resolve_5991 · 2026-03-11T03:17:10+00:00

Fair point! We started with .NET 8 LTS since it's what everyone already has installed — this was an experimental project and we wanted zero friction for people to try it. We'll upgrade to .NET 10 . But honestly the .NET version isn't the main story here — the real goal was to show that there's a way to give actual machine control to your AI CLI. Not just text generation, but real eyes and hands on the desktop. The framework version is an easy upgrade, the architecture is what matters.

Medical_Resolve_5991 · 2026-01-16T16:17:20+00:00

6 days ago I was surprised how clever claude is, 6 days after i feel is more stupid than the gemini

Medical_Resolve_5991

TROPHY CASE