Kruvo
EnglishPortuguês简体中文
Download
Menu

Tasks you can give Kruvo

Docs
Conceptual editorial image of project papers and a red pencil on a desk.

Six illustrative workflows show a task, the tools it uses and where approval is required. These are examples, not recorded customer runs or guaranteed outcomes. Connect the required tools first; computer use needs a compatible app and setup.

Review a repository for vulnerabilitiesDeveloper, before a releaseTerminal · Files · Specialist coworker

You ask

Review this repository for security issues and propose fixes.

Kruvo does
  1. The security coworker reads the code and dependency manifests in the workspace.
  2. Runs read-only checks in the terminal and rates each finding.
  3. Drafts a fix for each confirmed issue.
Stops for you

File changes and terminal commands follow your permission policy. Hard-floor operations always require human approval.

You get

security-review.md with findings, severity and proposed patches.

A morning briefing on your phoneFounder, 08:00Automation · Telegram · Gmail · Calendar

You ask

Every weekday at 8, send me what matters today: calendar, new emails that need me and open approvals.

Kruvo does
  1. Runs on schedule in a designated desktop session while Kruvo is running.
  2. Reads the calendar and the inbox and drafts a short briefing.
  3. Delivers it to configured Telegram when your permissions allow; approval requests wait for a person.
Stops for you

Unattended runs cannot approve themselves or use the browser and desktop apps. Eligible ordinary approvals can be answered in Telegram; hard-floor approvals stay in the app.

You get

A briefing message using the tools and schedule you configured.

Triage the inbox and draft the simple repliesOperations, after lunchGmail · Outlook

You ask

Sort today's inbox, archive newsletters and draft replies to the simple requests.

Kruvo does
  1. Groups messages by what they need: reply, forward, wait, archive.
  2. Drafts replies in your tone for the routine ones.
  3. Leaves anything ambiguous for you with a one-line summary.
Stops for you

A saved email draft does not send the email. Archiving and other connector actions follow your permission policy; review any standing grants.

You get

An organised inbox and drafts ready for you to review.

Log the week's hours in the timesheet portalConsultant, Friday 17:40Browser · CalendarBrowser

You ask

Fill in my timesheet for this week from my calendar and stop before submitting.

Kruvo does
  1. Asks once to use timesheets.example.com, then opens it in Kruvo's own browser profile.
  2. Reads the week's calendar and enters each day's hours and project codes.
  3. Shows every step in the live panel; you can pause or take over at any moment.
Stops for you

Submit is a sensitive action: the form waits for your click.

You get

Timesheet filled and a summary of hours per project.

Reconcile supplier invoices against the spreadsheetFinance, month endBrowser · FilesBrowser

You ask

Compare the invoices in the supplier portal with invoices.xlsx and list every difference.

Kruvo does
  1. Opens the supplier portal after your consent and reads the invoice list.
  2. Compares amounts, dates and references with the spreadsheet in your workspace.
  3. Prepares the differences with a link to each source.
Stops for you

Any download from the portal asks first; nothing is paid or approved.

You get

differences.xlsx with a row per mismatch.

Publish the weekly status report on the intranetEngineering lead, MondayJira · GitHub · Browser · SlackBrowser

You ask

Draft this week's status from Jira and GitHub, post it on the intranet page and tell #team.

Kruvo does
  1. Collects closed issues, open risks and merged pull requests from Jira and GitHub.
  2. Writes the report in the team's template and links every claim to its source.
  3. Opens the intranet in Kruvo's browser after your consent and places the draft on the page.
Stops for you

Publishing through the browser requires approval in the app. Slack follows your connector permission policy; read the draft and check any standing grant before sending.

You get

The report and sources, with publication and the team message subject to your permissions.

Permissions and limitations

  • Hard-floor actions always require human approval; standing grants do not lower these boundaries.
  • Computer actions classified as sensitive need approval in the desktop app. Scheduled automations do not use the browser or desktop apps.
  • Browser and Windows app access requires your consent. Pausing stops further work; it does not recall an external action already in flight.

Computer use requires a compatible 0.3.4 app and setup. Check the documentation and extension instructions against your installed version.

Download Kruvo