taskt

Jason Bayldon built taskt (originally named sharpRPA) to give Windows users a free, no-code robotic process automation client without vendor subscriptions. The project packages process recording, desktop UI clicks, and web tasks into a standalone C# application that runs entirely on local machines. Today, that origin means your automation scripts and execution logs remain on your local disk rather than streaming to a vendor cloud.

Why taskt instead of UiPath

UiPath dominates enterprise automation, but its commercial model requires cloud tenant registration, centralized orchestrators, and costly per-robot licensing. Even starter tiers route telemetry and workflow metadata through vendor cloud servers. taskt takes the opposite approach: it is a local desktop runner with no mandatory network dependencies. Scripts save as plain XML files on your own filesystem, and execution stays entirely on your Windows desktop without sending records to third parties. For users handling confidential spreadsheets or private client data, keeping automation logic on local hardware removes compliance risks.

The trade-off centers on enterprise governance. UiPath provides document understanding, machine learning models, process mining, and fleet orchestration across server farms. taskt provides none of that infrastructure; its optional server component remains experimental, and scheduling relies on Windows Task Scheduler. Choosing taskt means accepting simpler, self-contained desktop tasks rather than an enterprise-wide cognitive bot network.

What it does well

• Visual command builder: configure actions through dropdown menus and visual forms without writing C# or script syntax.
• Local spreadsheet automation: reads, updates, and calculates cells in Microsoft Excel without cloud connectors or paid add-ins.
• Screen and element recorder: records mouse clicks, keystrokes, and UI targets to draft automation sequences quickly.
• Desktop and browser coverage: drives native Windows programs and web applications using integrated Selenium drivers.
• File-based workflow storage: saves sequences as plain XML files for straightforward backups and local version control.
• Extensibility hooks: allows running custom C# snippets, PowerShell scripts, or batch commands when an edge case demands code.

Limitations