This was my first thought as well. This isn't a replacement for portainer agents on mulitple docker hosts, hopefully that's something that is doable in the future.
I ditched portainer earlier this year to use the command line only, and don't miss it at all. If you're only using docker compose, I really don't see the point of it.
UI, just too many annoyances. Fkr example the cut off unhelpfull error messages
compose files, like this project calls it are taken hostage by portainer
git, while you can use a repository there is no comfortable way to test out changes and commit them to git. Would portainer use a sinple file structure for compose files that would not be a problem
Ads, they try to promote there business version via the UI.
I could close my eyes to all of those, but the issue that pisses me off the most is that often enough Portainer just forgets which stacks it has ownership over, forcing you to delete the whole stack, dig up the old compose from its files, and create it again