Kruvo
Documentation

Getting started

Ten minutes from install to a finished deliverable.

1. Install

Download the installer for your platform from the download page and run it. On Windows the app installs for the current user; on macOS drag Kruvo to Applications. Kruvo checks for updates on launch and installs them only if they are signed with the Kruvo updater key.

2. Add a model

Open Settings → Model, pick a provider and paste your API key. Keys are stored in the app's local secret store and never leave your machine except to reach the provider you chose. To run fully local, install Ollama, pull a tool-capable model, and select Ollama as the provider.

A curated model list marks what we have verified for tool-calling work. Any model string works, at your own risk.

3. Your first task

Point Kruvo at a folder (it asks before reading anything outside it) and describe the outcome you want:

Review this repository for security issues. Run the scanners you have,
explain each finding, and prepare fixes I can approve one by one.

Kruvo plans the steps, works with its tools and asks before anything consequential. Deliverables land as files in the workspace and in the Artifacts panel.

4. Approvals and the audit trail

  • Hard floors: some operations are human-only in every mode (writing protected files, tools that grant persistent authority, anything irreversible).
  • Approvals: writes, sends and shell commands ask first. Approve once, or turn the approval into a standing rule for that exact action.
  • Auto-approve mode: a reviewer model lets routine actions through and escalates anything it is not sure about. Repeated denials pause the reviewer and hand control back to you.
  • Audit: Settings → Audit lists every tool call with who approved it and why.

Unattended runs (automations, messages from your phone) never self-approve. Their questions park in the Inbox until you answer, from the app or from the chat.

5. Work from Telegram

  1. Create a bot with @BotFather and copy the token.
  2. Open Connectors → Telegram, paste the token and connect. The status shows Ready only when the listener is actually receiving.
  3. Send your bot a direct message once. It is parked, because senders are denied by default.
  4. Back in the connector, under Messages from senders you haven't allowed, choose Allow & deliver.
  5. In Inbox → Configure → Direct messages, pick the session that should handle your DMs.
  6. Send a new message. Replies come back to the chat automatically, and questions Kruvo needs answered arrive there too.
Only one process may poll a Telegram bot at a time. If the status says Not receiving with a conflict reason, stop the other process (an old script, a second install) and the listener recovers on the next message.

6. Work from Slack

Create a Slack app with Socket Mode, add the bot to a channel and mention it: @Kruvo check where the release stands. A session opens on your desktop and the answer comes back as a thread reply. One-click installation through Kruvo Cloud is part of the Pro plan.

7. Automations

Automations run a task on a schedule: a morning brief from your calendar and inbox, a weekly report, a standing watch over a channel. Every run keeps a full transcript, and approvals go to the Inbox.

8. Where your data lives

Everything is local: %APPDATA%\kruvo on Windows, ~/.config/kruvo on macOS. Conversations are append-only files you can read, connector tokens and model keys sit in the secret store with user-only permissions, and deliverables go to the workspace you chose (default ~/Kruvo).

FAQ

Is it really free?

Yes. The Free plan has no time limit and no capability locks; see pricing for what Pro and Team add.

Which models work best?

Models with reliable tool calling. The curated list in Settings marks the ones we test with.

Can I use it without any cloud account?

Yes. Kruvo Cloud is optional and off until you sign in.

Where do I report a security issue?

[email protected].