Devolutions / Devolutions/UniGetUI

[IMPROVEMENT] Add some automation capabilities or integrate an AI powered system

Open
#5,027 2 comments 2 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
26.1k
Forks
924
Avg merge
15h 52m
Merged PRs (30d)
52

Description

### Please confirm these before moving forward.

- [x] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- [x] This improvement refers to an existing feature. If you want to suggest a new feature, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=new-feature&projects=&template=feature-request.yml&title=%5BFEATURE+REQUEST%5D+%28Enter+your+description+here%29).
- [x] This improvement is not a bug. If you want to report a bug, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=bug&projects=&template=bug-issue.yml&title=%5BBUG%5D+%28Enter+your+description+here%29).

### Describe the improvement

Hi,

I really think it is the moment we can delegate some of this annoying (even though somehow delightful) feeling of updating and maintaining our software packages patched for the 0day, etc. Thus, this software is a life-saver, as it literally reduces the amount of effort and time that must be spent to do the updates and remind oneself or create scripts that will do it, even with LLMs it it would be tedious, unless we vibe-code something like this and add what is missing with a prompt, presets, or templates and adjust everything just like that, including having access to some capability of creating them, but there are software that can take care of that, unless what will follow convince you.

What I want to have is an AI that can be integrated to read the logs, and get some instructions about what to do in the future per software, package, package-manager, and several other automation-related events... so less will need our immediate attention, and we can adjust it to be just a few words or a verbose journal where relevant chunks of logs to us are integrated, and even show a log of everything already analyzed, researched, and either authorized to fix and then fix it or make it part of the generated document that we will read and that can be formatted also in whatever way we like! So make it possible that we will have something like that, even via some pipe of everything to some local ai inferenced model that we can pick everything about (protocols, structure, etc.) sort of open and reliable way to do things properly, so we set a system around it that will know what files to analyze and when, etc. to generate something via a prompt by treating every previous information as part of the codebase, that must be processed, thus making this sort of aware of whatever get installed, patched, fixed, installed, uninstalled, etc. and keep track of files but also registry entries and everything fucking thing sorry about that but it was a necessary rant, I think you may like the idea yourself as you will be able to delegate it to, but make this more accessible, more intelligent, having it become something that can keep the system as errors and problems free as possible, as stable and performant as possible, and this can be done, we can delegate some processing to a frontier SOTA model that will get perfectly anonymized everything (I got another idea and thought but I will limit this to just the feature request).

### I have plenty of ideas if someone would like to hire me!

### Describe how this improvement could help users

So it becomes possible to either use the software GUI to know more about something or just ask an LLM at any moment and get an answer, or have something generated automatically. We can even interact with the software via SDK, API, MCP… or whatever else! And use Obsidian, for example, or a browser to get informed in some centralized dashboard… so we can see when something needs our attention. If we want to have a sort of HUD, always-in-sight dashboard, or super minimalist one, and anything in between… Everyone's system-situation, action-potential, taste, and style will decide for them.

This will also help with any other automation that will be part of everyone's (almost) future! As by the end of the day we all want a working system that is bug-free and feature-rich, etc. To do not spend the time forcibly reading logs and notifications…

Contributor guide

Open the contributing guide

Research direction

The proposal names no files, tests, or existing entry points. Start by mapping the current GUI, package-manager update flows, logs, and registry handling, then assess how an SDK, API, MCP integration, or local model could fit. The request needs a narrower first milestone and explicit acceptance criteria before implementation can be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
machine-learning
Domain
ai, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.