Skip to content

Rynne 1.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Aug 10:06
· 32 commits to main since this release

Rynne 1.0.0

The first public release of Rynne, a local AI agent for Windows that goes beyond chat.

Give Rynne a goal in plain language. It selects the right tools, performs the work on your computer, verifies the outcome, and shows every step in the desktop interface.

What's included

  • Windows, application, file, terminal, Git, and browser automation;
  • voice input, wake word detection, Russian and English UI, and configurable TTS;
  • Groq, OpenRouter, and Gemini support with multiple API keys and custom models;
  • reusable skills, memory, background tasks, automations, MCP integrations, and recovery paths;
  • Telegram Business integration and remote control through a Telegram bot;
  • three permission modes with approval gates for protected actions;
  • experimental proactive assistance through Rynne Nearby;
  • parallel subagents when multiple independent API keys are available;
  • detailed live execution logs and result verification.

Installation

  1. Download Rynne_1.0.0_x64-setup.exe from the assets below.
  2. Run the installer.
  3. Add at least one Groq, OpenRouter, or Gemini API key in Rynne Settings.
  4. Give Rynne a task in plain language or enable voice control.

The installer is not code-signed yet, so Windows SmartScreen may display a warning. Verify the accompanying SHA-256 checksum before installation if needed.

Try these commands

  • “Open Obsidian, create a note with a poem about space, and verify that it was saved.”
  • “Open OpenRouter Activity in the browser and take a screenshot.”
  • “Find the error in this project, fix it, and run the tests.”
  • “Send this message to a Telegram contact after resolving the correct recipient.”

Important notes

Rynne 1.0 is an early public release. Voice interaction, automation of third-party applications, and proactive assistance still need broader real-world testing. Please report reproducible failures and include the visible execution log whenever possible.