Galactic Key · Tricon workbench · 28 October 2026

Tricon ran a real browser, on a private screen, after one yes

You type a sentence. Tricon offers the action. You click Allow. Chromium opens on an invisible Linux screen, goes to the address, and Tricon shows you a picture from before and after.

2.9 s

private screen ready → the page loaded

1 of 1

computer actions Tricon runs after your yes

times it touches your own screen

Try it yourself

Open tricon-workbench.berkle.space and type exactly:

take a screenshot of https://example.com

An Allow card appears. Click Allow. Two pictures and a timed log come back in the same thread.

What actually happened in this run

The private screen before: an empty Chromium window

Before — an empty Chromium window on the private screen

The private screen after: example.com loaded

After — example.com, loaded and rendered

0 ms	display :99 ready (1280x1024)
997 ms	browser window open: about:blank — Chromium
1354 ms	screenshot before
1360 ms	focus browser window
1391 ms	key ctrl+l (address bar)
1636 ms	type url (19 characters)
1655 ms	key Return
2925 ms	page title: Example Domain — Chromium

Every line above is from the run's own log. The page title line is the browser reporting the loaded document, not a caption.

Why it is safe to hand over

The screen is a private virtual display on the workbench machine. It is not your Mac, it is not your monitor, and it is empty until the action runs. Nothing happens without your yes: the action sits as an offer until you click.

What it does not do yet

It cannot read or press windows on your own Mac. That needs a macOS permission only you can grant, so Tricon's own rules keep it off the pick list rather than reaching for your screen.