Technology·Stockholm ·
Aido 1.2.0 lets teams adopt its AI code review by pinning a single workflow file
The open-source, multi-provider AI reviewer for GitHub can now be installed with one thin workflow instead of copying about 30 files, and upgrades become a one-line tag bump.
Aido, the open-source multi-provider AI assistant for GitHub code review, has released version 1.2.0. The headline change is remote install: teams can now adopt Aido by pinning a release tag in a single workflow file, rather than copying roughly 30 files into their repository.
Aido lets development teams review, summarize, explain, and document code by commenting on a pull request. It works with Gemini, ChatGPT, and Claude, and runs inside GitHub Actions on a team's own provider keys.
One file instead of thirty
With remote install, a repository references Aido's published workflow directly and passes its own provider keys as secrets. Aido runs entirely in the repository's own context: its event, its GITHUB_TOKEN, and its secrets, with no access beyond what the workflow grants. Teams can still customize behavior by adding configuration overlays without copying any scripts, and upgrading becomes a one-line tag bump. Existing copy-based installations continue to work unchanged.
Restored pull request commenting
Version 1.2.0 also fixes a permissions regression. An earlier change had reduced five commands, summarize, explain, docs, suggest, and test, to read-only access, which GitHub rejects when posting a comment on a pull request. The release restores write access so those commands can post their results again. Teams that copied those workflow files should re-copy them or change the permission back to write.
A new label-gated smoke test now runs an end-to-end remote install on demand, and caught the permissions regression on its first run.
Version 1.2.0 is available now on GitHub.
More press releases
Aido 1.1.0 adds a first automated test suite and a shared internal library
The open-source multi-provider AI code-review tool for GitHub ships 66 unit tests, an internal library refactor that removes roughly 945 lines, and two dependency security fixes.