Skip to main content
Kyro is an open-source product fromTonmoy InfrastructureOwned byEshan Roy
Kyrov0.1.0
Get Kyro
Practical Workflows

Real Problem-Solving with Kyro

Every use case below follows a structured, verified execution path tested against the Kyro runtime. No synthetic case studies, exaggerated metrics, or invented customer testimonials—just concrete steps and required prerequisites.

Everyday Workflows (Non-Developers)

File maintenance, confidential document analysis, and visual diagnostics.

Everyday Mode

Safe Local Directory Cleanup & Deduplication

Everyday Users
The Problem

Downloads and project folders quickly accumulate disorganized PDFs, images, archives, and duplicate downloads with duplicate filenames (e.g. 'file(1).pdf'), consuming disk space and creating clutter.

Kyro's Verified Capability

Safe Reversible File Organizer with SHA-256 content deduplication, extension-based categorization rules, destination collision handling, and rollback manifests.

Step-by-Step Workflow

  1. 1Select a target directory (such as ~/Downloads) in Kyro's Everyday Mode.
  2. 2Kyro scans the tree, computes SHA-256 hashes to group byte-for-byte identical files, and drafts a proposed reorganization plan.
  3. 3Review the interactive preview showing exact source and destination paths.
  4. 4Click Execute to safely relocate files and archive duplicate copies into a dedicated duplicates folder.
  5. 5If the result is not desired, click 'Rollback' at any time to restore every file back to its original location using the SQLite transaction manifest.
Important Prerequisites: Standard user filesystem read and write permissions to the targeted directory. Available disk space to move files within the same filesystem volume.
Documentation

Confidential Document Extraction & Revision Diffing

Everyday Users
The Problem

Users need to extract critical dates, action items, and contractual commitments from multi-page PDFs or compare two contract revisions, but cannot upload confidential business files to cloud-hosted web AI tools.

Kyro's Verified Capability

Local-First Document Assistant with native Rust PDF stream decompression (FlateDecode), Tj/TJ text operator extraction, regex date parsers, and side-by-side diff viewers.

Step-by-Step Workflow

  1. 1Drop or browse a local PDF or text document into the Document Assistant modal.
  2. 2Kyro parses the raw PDF streams locally in Rust without sending document bytes over the network.
  3. 3Review the structured summary listing extracted dates, milestones, and pending action items.
  4. 4Select a second revision to view a visual side-by-side diff highlighting all added, deleted, and modified text blocks.
  5. 5Optionally send specific extracted text fragments to your configured model for tailored summarization.
Important Prerequisites: Standard unencrypted PDF or plain-text file on local disk. Configured LLM endpoint if conversational synthesis of the extracted text is requested.
Documentation

Software Engineering Workflows

Dev server management, git worktrees, compiler triage, and automated visual QA.

Dev Workbench

Autonomous Web UI Regression & Responsive Auditing

Software Engineers
The Problem

Refactoring frontend code or updating styling dependencies frequently introduces unintended layout shifts, responsive breakages on mobile screens, or broken image links that are difficult to catch manually.

Kyro's Verified Capability

Autonomous UI Audit Workflow with multi-viewport baseline comparisons, pixel diff calculations, and markdown defect reports.

Step-by-Step Workflow

  1. 1Open Developer Workbench and point Kyro to your web project directory.
  2. 2Kyro boots the local development server (e.g. Next.js on port 3000 or Vite on port 5173) and extracts discovered routes.
  3. 3Kyro launches a browser session via WebDriver BiDi or CDP, capturing full-page renders at Desktop (1920x1080), Tablet (768x1024), and Mobile (375x812) viewports.
  4. 4The Visual Regression Engine compares renders against saved baselines in ~/.config/kyro/baselines/, flagging layout shifts with exact pixel percentage differences.
  5. 5Review the aggregated markdown audit report detailing console errors, accessibility warnings, and visual diff screenshots.
Important Prerequisites: Local Node.js environment with project dependencies installed. Supported browser (Firefox, Chromium, Chrome, Brave, or Edge) installed locally.
Documentation

Parallel Feature Development with Git Worktree Isolation

Software Engineers
The Problem

Autonomous AI coding agents frequently overwrite uncommitted developer edits, corrupt the git index, or conflict with each other when attempting multiple parallel tasks on the same repository.

Kyro's Verified Capability

Multi-Agent Workspace with specialist bot roster (Apex, Forge, Scout) executing in isolated Git worktrees with reviewed reconciliation.

Step-by-Step Workflow

  1. 1Initiate a complex feature request in the Dev Workbench.
  2. 2Kyro divides the initiative across specialist agents: Scout explores repository architecture, Forge writes code, and Apex orchestrates integration.
  3. 3Kyro creates isolated Git worktree checkouts for each agent, allowing Forge to compile and test code without touching your primary working directory.
  4. 4Each agent completes its subtask and records status updates in the roster timeline.
  5. 5Review the final unified diff in the reconciliation panel before approving the branch merge into your working tree.
Important Prerequisites: Git repository on local disk with clean commit history. Sufficient disk space for secondary worktree clones.
Documentation

Automated Compiler Diagnostic Triage & Repair

Software Engineers
The Problem

Cryptic compiler errors (such as Rust borrow checker errors or TypeScript type mismatches) interrupt development flow, requiring developers to manually parse verbose terminal output.

Kyro's Verified Capability

Build Doctor automated diagnostic engine with compiler error parsing and unified diff patch synthesis.

Step-by-Step Workflow

  1. 1Run your build or test command from Kyro's integrated terminal or trigger Build Doctor upon task failure.
  2. 2Build Doctor parses the raw stderr stream, extracting Rust error codes (error[E0382]), TypeScript codes (TS2322), or Vitest failure assertions.
  3. 3The engine pinpoints the exact offending file, line number, and column.
  4. 4Build Doctor inspects surrounding code context and synthesizes candidate fix patches formatted as unified diffs.
  5. 5Review the proposed code change and apply it with one click or pass it to Forge for regression verification.
Important Prerequisites: Standard compiler or test runner output streams. Workspace path located within an authorized directory tree.
Documentation

Automated Desktop Routines with Mobile Telegram Alerts

Technical Teams
The Problem

Teams need recurring desktop maintenance routines (such as nightly build verifications or status checks) to run unattended, with immediate notifications delivered to mobile devices.

Kyro's Verified Capability

Teach-a-Task recorder, timezone-aware cron routine scheduler, and Telegram Remote Bridge with fail-closed authentication.

Step-by-Step Workflow

  1. 1Record a demonstration sequence in Kyro or construct a prompt workflow with required tools.
  2. 2Configure a schedule using standard cron expressions with explicit IANA timezone support.
  3. 3Attach your Telegram Bot token and allowed chat ID in Kyro Settings (stored securely in the OS Keyring Vault).
  4. 4Kyro executes the routine in the background at the specified interval, respecting concurrency overlap guards.
  5. 5Receive real-time execution summaries and interactive approval requests directly on your phone via Telegram.
Important Prerequisites: Computer powered on and active at the scheduled trigger time. Telegram bot token and personal chat ID for remote bridge functionality.
Documentation

Secure GitHub Automation via Model Context Protocol (MCP)

Technical Teams
The Problem

Developers want their local AI assistant to interact with GitHub issues, pull requests, and repository metadata without exposing personal access tokens in plaintext or giving the agent unchecked write permissions.

Kyro's Verified Capability

Native GitHub Connector with PKCE OAuth 2.0, single-flight token refresh, and per-action governance policies (Allow, Ask Always, Deny).

Step-by-Step Workflow

  1. 1Open Connections in Kyro and click 'Connect GitHub'.
  2. 2Authenticate via secure browser OAuth 2.0 with Proof Key for Code Exchange (PKCE).
  3. 3Kyro stores the bearer token inside the OS Keyring Vault, ensuring it is never stored in plaintext or exposed to frontend logs.
  4. 4Kyro discovers available GitHub MCP tools (list_issues, create_pull_request, get_commit).
  5. 5Configure per-action governance: set read-only commands to SafeAutoApprove and write commands to AskAlways.
  6. 6Direct Kyro in chat to inspect an open issue, write a bug reproduction script, and submit a draft PR.
Important Prerequisites: Active GitHub account. Configured OAuth application client credentials or Kyro standard GitHub connector.
Documentation