@simular-ai/simulang-js
simulang-rs, a Rust crate published by Simular, built with napi-rs. Provides high-level primitives for desktop automation — keyboard and mouse input, screenshots, clipboard access, audio capture, accessibility-tree inspection, and more — exposed through idiomatic JavaScript. Ships TypeScript definitions auto-generated from the Rust source, so the types always match runtime behavior.
Install
Node.js 20 or newer is required. If your platform isn’t covered, see Building from source.
Optional — install the log viewer
Thelog-window.mjs example uses @simular-ai/simulang-log-viewer, which is declared as an optional peer dependency and not installed by default. Install it only if you want to run that example or use the same pattern in your own code:
Usage
Try the includedgoogle_search.mjs example — it opens Google in Chrome, enables the accessibility tree, takes a screenshot, and displays it:
API documentation
Browse the API reference for more details. A bleeding-edge preview of HEAD onmain is also published to GitHub Pages between releases.
Using with Claude Code
This package ships a shortCLAUDE.md inside the npm tarball that points Claude Code at index.d.ts as the source of truth for the API and adds a few cross-cutting notes that types alone can’t express (lifetime rules, coordinate system, etc.). Wire it into your project’s CLAUDE.md with:
@./node_modules/@simular-ai/simulang-js/CLAUDE.md import inside a sentinel-delimited block — safe to re-run, no-op when already present.
Relationship to simulang
@simular-ai/simulang is a CLI that runs desktop automation scripts (.ts, .js, .simulang) using this package. It bundles simulang-js and re-exports the full API to scripts, so you can write and run automation scripts without a build step:
simulang-js is the underlying primitive library; simulang is the batteries-included script runner built on top of it. If you are embedding desktop automation into your own Node.js application, depend on simulang-js directly. If you just want to run standalone automation scripts, simulang is the easier starting point.
You can also point simulang at a local simulang-js checkout during development:

