October 2, 2026
Keep building your app in one chat: Row-Bot 5.0 keeps the project with the conversation
Files, tasks and the terminal are now tied to the conversation where you build an app or presentation.

In Row-Bot 5.0, released on Oct 1, the AI agent continues its task between messages and resumes it after the app restarts.
Row-Bot runs as a standalone local AI assistant. In a single conversation, you can request an app or presentation, view the result, make revisions and keep working. The development panel includes files, changes, Git and an interactive terminal. The Design panel handles preparing, editing, checking, exporting and publishing the result.
Tasks persist. The agent runs without a default turn limit, but you can limit its runtime or number of turns. If work stops progressing, the agent pauses the task. You can see delegated agents' progress, send them a message or stop them.
Previously, requests to approve actions expired after 30 minutes by default. They now persist after a restart, and you can respond from the conversation or the attention list. Rejecting a request ends the agent's current turn.
Installation and models. An installer is available for Windows 10/11 x64, a DMG for macOS Apple silicon, and the developer provides a script to install version 5.0.0 on Linux. After installation, open the app and select your first model: new profiles have no model assigned in advance. You can connect Ollama, a ChatGPT, Claude or Grok subscription, an API key or your own endpoint. Row-Bot checks the selected model and marks it unavailable when its provider is removed, without automatically choosing a replacement.
The developer replaced the previous NiceGUI interface with a single React app for computers, browsers, phones and tablets. Settings now has search, drafts are preserved when reconnecting, and conversations can be exported to Markdown and PDF.
Row-Bot is free and does not require its own subscription. Models and external services may incur separate charges.
Users of Thoth and early Row-Bot builds need to run the previous release with migration support before upgrading to 5.0.0.
