terminator-rs 0.22.0

A Playwright-style SDK for automating desktop GUI applications
docs.rs failed to build terminator-rs-0.22.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

terminator 🤖 Mediar.ai

https://github.com/user-attachments/assets/b7bec5df-64a9-4f0e-aba4-1578c11275c7

🚀 What's new

AI-powered desktop automation — open source, MIT-licensed, cross-platform, accessibility-first. Works across all apps and browsers. Inspired by GitHub Actions & Playwright. 100x faster than generic AI agents, >95% success rate, no vendor lock-in.

🧠 Why Terminator

For Developers

  • Create automations that work across any desktop app or browser
  • Runs 100x faster than ChatGPT Agents, Claude, Perplexity Comet, BrowserBase, BrowserUse
  • >95% success rate without costly consultant armies (UIPath, Automation Anywhere)
  • MIT-licensed — fork it, ship it, no lock-in

We achieve this by pre-training workflows as deterministic code, and calling AI only when recovery is needed.

For Teams

Our public beta workflow builder + managed hosting = n8n for data entry automation in legacy systems:

  • Record & map your processes in 5 mins
  • Deploy AI to execute them at >95% success rate
  • Kill repetitive work without legacy RPA complexity or cost

🎯 Choose Your Path

🤖 Want AI Automation with Claude Code? (Recommended for Most Users)

Install the Terminator MCP in Claude Code:

claude mcp add terminator "npx -y terminator-mcp-agent@latest" -s user

Or install via the MCP directory for other clients (Cursor, VS Code, etc.).

What this does: Gives AI assistants the ability to control your desktop and automate tasks across any application.

To create workflows, please download the desktop app.

Feature Support

While Terminator aims for full cross-platform support, current capabilities vary by OS. Windows is the primary development target and has the most complete feature set.

Feature Windows macOS Linux Notes
Core Automation
Element Locators ✅ 🟡 🟡 Find elements by name, role, window, etc.
UI Actions (click, type) ✅ 🟡 🟡 Core interactions with UI elements.
Application Management ✅ 🟡 🟡 Launch, list, and manage applications.
Window Management ✅ 🟡 🟡 Get active window, list windows.
Advanced Features
Browser Automation ✅ ✅ ✅ Chrome extension enables browser control.
Workflow Recording ✅ ❌ ❌ Record human workflows for deterministic automation.
Monitor Management ✅ 🟡 🟡 Multi-display support.
Screen & Element Capture ✅ ✅ 🟡 Take screenshots of displays or elements.
Language Bindings
Python (terminator.py) 🟡 🟡 🟡 pip install terminator
TypeScript (@mediar-ai/terminator) ✅ ✅ ✅ npm i @mediar-ai/terminator
MCP (terminator-mcp-agent) ✅ ✅ ✅ npx -y terminator-mcp-agent --add-to-app [app]
Rust (terminator-rs) ✅ ✅ ✅ cargo add terminator-rs

Legend:

  • ✅: Supported - The feature is stable and well-tested.
  • 🟡: Partial / Experimental - The feature is in development and may have limitations.
  • ❌: Not Supported - The feature is not yet available on this platform.

🕵️ How to Inspect Accessibility Elements (like name:Seven)

To create reliable selectors (e.g. name:Seven, role:Button, window:Calculator), you need to inspect the Accessibility Tree of your OS. Here's how to explore UI elements on each platform:

🪟 Windows

  • Tool: Accessibility Insights for Windows
  • Alt: Inspect.exe (comes with Windows SDK)
  • Usage: Open the app you want to inspect → launch Accessibility Insights → hover or use keyboard navigation to explore the UI tree (Name, Role, ControlType, AutomationId).

These tools show you the Name, Role, ControlType, and other metadata used in Terminator selectors.

🍎 macOS

  • Tool: Accessibility Inspector
  • Usage: Comes with Xcode → Open Xcode > Open Developer Tool > Accessibility Inspector → Use the target icon to explore UI elements on screen.

🐧 Linux

  • Tool: Accerciser

  • Install:

    sudo apt install accerciser

  • Usage: Launch Accerciser → Select the window/app → Browse the accessible widget tree.

Explore Further

Troubleshooting

For detailed troubleshooting, debugging, and MCP server logs, send us a message.

Contributing

Contributions are welcome! Please feel free to submit issues and pull requests. many parts are experimental, and help is appreciated.