What is tinycomputer?

A decision-model-based harness for desktop and browser automation written in Rust. It drives apps like Mail and Notes and websites in a real Chrome browser, and it is distributed as a TinyBus module that a host program loads.

How does Jev drive the automation?

Every choice about what to press comes from Jev: it answers small, closed questions about the screen, and the rest of the system is plain Rust that reads the screen, asks the questions, checks the answers, acts and verifies.

Does it use screenshots or pixel matching?

No. It reads the screen the way a screen reader does — as a list of named buttons and fields — so nobody has to tell it where the buttons are, and it avoids the brittleness of pixel coordinates.

Can I give it a multi-step job?

Yes. Hand over a job in plain words; a planner turns it into steps and tinycomputer carries them out across the browser and desktop apps. The README's example is finding the cheapest Delhi-Srinagar flight on 14 October and filling details up to payment.

Will it spend money or make irreversible changes?

The README says it always stops before money moves, and it pauses for a missing detail or your approval, with the harness enforcing safety rules around actions. The full list of guards was cut off in the digest excerpt.

Who built tinycomputer?

Tinyhumansai, the same organisation behind the tinyjevclient Rust SDK for TypeSafe's System One API. Metadata: Rust, GPL-3.0, 6 stars, 9 forks, created 2026-08-23 and pushed 2026-10-17, so it is actively developed.

What is a TinyBus module, and how do I run it?

A TinyBus module is one library that a host program loads and that an agent then calls — tinycomputer is built that way, rather than shipping as a standalone app. The digest does not capture the install or host integration steps.

Jev directory

CommunityJev Agents & MCP

Tinycomputer

A Rust harness for desktop and browser automation where every choice about what to press comes from Jev: the decision model answers small closed questions about the screen while plain Rust reads the screen as named buttons and fields, acts, verifies and enforces the safety rules. It stops before money moves.

See highlights Open github.com

Stars: 6
Language: Rust
License: GPL-3.0
Reading time: 3 min
Published by: Community
Author: tinyhumansai
Last verified: Oct 2026

tinyhumansai/tinycomputer

Organization repository on GitHub

View on GitHub

Decision model (JEV) based harness to perform Desktop & Browser automation. Written in Rust.

Forks: 9
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.

Tagscommunity github rust automation desktop

Works forJev for Realtime control Jev for Decision gating

Used inJev for Software & DevTools

Languages: Rust
Platforms: Browser
Capabilities: Open sourceRuns locally

Highlights

Every choice about what to press comes from Jev, which answers small, closed questions about the screen.
Reads the screen like a screen reader — named buttons and fields — with no screenshots or pixel matching, and nobody tells it where buttons are.
Plain Rust code asks the questions, checks answers, acts, verifies what happened and enforces the safety rules.
Sample job: cheapest flight Delhi to Srinagar on 14 October, details filled up to payment; it stops before money moves.
Ships as a TinyBus module: one library a host program loads, which an agent then calls.

Watch out

README reviewed 2026-10-17; the digest truncates the 'What it can do' list after the first two bullets, so setup, model access, supported platforms and any performance numbers are not captured. The GPL-3.0 licence and the Jev-based design are stated in the visible README text.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

MCP tool routing: Jev in front of the tool call

Oct 16, 2026

Tool menus can outgrow the context that reads them. The catalog's Jev-based routers and gates narrow the list: benchmarked tool search, per-tool scoring, fail-closed approvals, and WebMCP in the browser.

Jev Agents & MCP#mcp#tool-routing#agents

Read article

Approval policies for coding agents: hooks, guards, and gateways