Technology·Stockholm ·

Aido now supports any OpenAI-compatible model and adds a weekly digest of merged pull requests

Versions 1.5.0 and 1.6.0 of the open-source, multi-provider AI code-review tool for GitHub let teams point it at any OpenAI-compatible endpoint, including DeepSeek, Kimi, Grok, Mistral, OpenRouter, and self-hosted gateways, and add a scheduled summary of the pull requests merged each week.

Aido, the open-source multi-provider AI assistant for GitHub code review, has released versions 1.5.0 and 1.6.0. Together they widen the range of AI models Aido can use to almost any OpenAI-compatible endpoint, and add a scheduled digest that reports what a team shipped.

Aido lets development teams review, summarize, explain, document, and triage code by commenting on a pull request, or automatically on the pull requests their AI agents open. It works with Gemini, ChatGPT, and Claude, and runs inside GitHub Actions on a team's own provider keys.

Any OpenAI-compatible model

Version 1.5.0 adds a generic OpenAI provider. Alongside the built-in Gemini, ChatGPT, and Claude support, teams can now point Aido at any endpoint that speaks OpenAI's chat completions API by setting the provider to OPENAI with a base URL and model name. That covers hosted models such as DeepSeek, Kimi, Grok, Mistral, and OpenRouter, as well as self-hosted gateways, so a team can run its reviews on the model, price, or private deployment it prefers. The sampling temperature is opt-in, sent only when a team configures it, for the widest compatibility.

A weekly summary of what shipped

Version 1.6.0 adds a scheduled digest. On a configurable window, seven days by default, Aido summarizes the pull requests merged in that period and posts the summary to GitHub Issues or Discussions, including a count of how many were authored by AI agents. It skips posting when nothing merged, so quiet weeks stay quiet.

Review verdicts that follow the recommendation

Version 1.6.0 also sharpens how a review is posted. Aido's GitHub review event now follows the review's own recommendation rather than the number of comments: a clear approval is posted as an approval, an approval with minor changes as a plain comment, and a request for changes as a formal change request. If GitHub rejects the formal event, Aido retries once as a comment so the review still lands. Inline suggestions that only repeat the code already in the file are now filtered out, keeping the review to changes that actually change something.

Versions 1.5.0 and 1.6.0 are available now on GitHub. Remote installs on the moving version-one tag receive the updates automatically; pinned installs upgrade by bumping the tag.

ShareXLinkedIn

More press releases