Getting started with Kruvo

1. Install

Download the installer for your platform, open Kruvo and choose the folder where it may work. The app creates its state in your user profile and never needs administrator rights for ordinary use.

2. Add a model

Open Settings → Models. Add a supported provider key or select Ollama for a local model. Provider keys stay in the local secret store.

3. Describe a task

Start with a task you can check: prepare a brief from this folder, review this repository, or compare open work in Jira and GitHub. Specify the output and the sources Kruvo should use.

4. Review approvals

Tools follow the permission policy and standing rules you configure. When approval is required, Kruvo shows the tool, target and reason. Approve, deny or redirect it. Hard-floor actions always require human approval.

• Check the target and arguments.
• Never paste secrets into a transcript.
• Create standing rules only for actions you understand and expect.

5. Work from Telegram or Slack

Configure channel credentials in Settings, allow the senders you trust and select the desktop session for their work. Keep Kruvo running on the computer. Configured senders can request work, receive replies and answer eligible ordinary approvals in Telegram or Slack.

Computer-use and hard-floor approvals must be answered in the desktop app. Remote messaging is not a separate device-handoff workflow.

6. Schedule recurring work

Create a local automation for a brief, report or channel watch. Kruvo must be running at the scheduled time. Unattended runs cannot approve themselves; requests wait for a person. Scheduled work excludes browser and desktop-application tools.

7. Let Kruvo use the computer

Use a compatible Kruvo app for supervised browser work and, on Windows, authorised foreground applications. Check the download page for the current public installer versions. Extension mode uses a version-matched package with the correct identity and native-host configuration.

Open Settings → Computer and turn on “Let Kruvo use the computer”. It is off by default. Consent is granted per site or app, with standing grants you can see and revoke.

For browser plans, choose “Approve & run with supervision”. Ordinary clicks and typing then run under supervision, with Pause, Take over and Stop in the live panel. Esc twice is an emergency shortcut in a focused Kruvo-owned extension tab with an active connection, and during Windows control when the keyboard hook is available. Use Pause in the app when the shortcut is unavailable. Pausing stops further work but cannot recall an operating-system or external effect already in flight.

• Computer actions classified as sensitive require approval in the app in every mode; unverifiable targets are treated as sensitive.
• One active browser session; on Windows, control one authorised foreground application at a time. Scheduled automations do not use browser or desktop tools.
• Choose Chrome or Edge in Kruvo's own profile, or your signed-in browser through the extension. The extension requires its own consent, a compatible version and native-host registration; check the extension instructions before installation.

8. Projects, tasks and modes

Chat answers without tools. Work runs in a folder you choose, with files, terminal and connectors. Group related sessions into a project with its own folder, keep a personal task list next to the conversation and switch the app between eight languages in Settings.

9. Coworkers, teams and other computers

Settings → Coworkers lists the coworkers on this computer. Enable the ones you want to use, or choose Create a coworker to write one in the app; it goes through the same permission review as an installed coworker. Kruvo 0.3.16 includes two team personas, Team Lead and Generalist.

To build a team, start a conversation with Team Lead, describe the goal and approve the team it proposes. A lead can staff other leads as managers. Each manager runs its own team on its own board and reports to the level above, up to four levels.

When computers are signed in to the same Kruvo account, the default coworker and team leads can see the enabled coworkers on each computer, together with that computer's operating system, computer-control access and connectors. They can draft a plan that assigns steps to coworkers on different computers. A team can also include a member on another computer: each item assigned to it runs there as a one-step plan, and the result returns to the team board.

Nothing in a plan runs until you review and approve it, and each item for a member on another computer needs your approval. Per-tool approvals and local permissions still apply on the computer that does the work.

• Tasks → Organisation shows the org chart, what each member is working on, and Pause and Resume for a team and every team below it.
• A top-level team and all of its sub-teams share a budget of 150 automatic wake-ups per hour.
• The Recent plans panel lists recent plans with the coworker assigned to each step.
• Steps and results that move between computers pass through the Kruvo Cloud relay. A member on another computer keeps no conversation between items; the team board holds the context.

10. Know where data lives

Conversations, audit records and credentials stay in the Kruvo profile on your machine. Deliverables stay in the workspace you selected. External data is sent only to the model and integrations required for the task. Screenshots taken during browser work go to the model provider for that task and are kept only as thumbnails in the local session.