FOR AI AGENTS AND TEST AUTOMATION

Build a screen. See it. Test it.

Describe a screen as JSON. Aster draws it with no window, browser or graphics card, and hands back the picture and every control on it.

An app described as JSONDrawn by Aster

Made for the loop

Every step is a plain call your agent or your test can make.

It can see what it built

One command draws the screen to a picture. No window, browser or graphics card.

Every image in our gallery was made with no screen.

It can read every control

Get each element's role, label and position as text. Click by label.

Role, label and position for every element.

Same input, same picture

No wall clock and no graphics card are involved, so pixel tests don't flake.

125 example screens, rendered twice: 0 differences.

Mistakes show up in the picture

Bad JSON is refused with a reason. An unknown element draws a red marker with its error code.

The model sees its typo and fixes it.

The loop

Three commands. The same calls are in the C library and in the Node.js and .NET bindings.

  1. 1aster shot app.json out.pngDraw the screen to a picture.
  2. 2aster tree app.jsonList every element with its role, label and position.
  3. 3aster click app.json "Save"Click by label, then list the tree again.
A small form, X-ray on: every switch, field, checkbox and button is outlined with its role and name.Drawn by Aster
3 more things the JSON can do

About 60 kinds of element

Layout, text, forms, tables, charts, Markdown and highlighted code, dialogs and menus.

Change it while it runs

Your process can send a new screen from any thread. The window updates on its next frame.

Every frame of motion

Step the animation clock by hand and capture each in-between frame. The same steps give the same frames.

Example scenarios (illustrative)

Read 3 short examples

An assistant that builds desktop tools

Someone asks a chat model for a plant-watering tracker. The model writes one file, renders it, looks at the picture and fixes the layout before handing it over.

Screen tests without a browser

A team's build renders every screen and compares it with a saved picture. A change comes back as an image with the moved pixels in red.

Renders you can repeat

A release video is rendered from the app itself, one frame per clock step. Render it again and every frame matches.

Good to know

  • JSON describes the widget kit. Effects like light, glass and smoke need Rust.
  • JSON apps run on the desktop and headless, not in a web page. The JavaScript library runs in Node.js.
3 more to know
  • There's no ready-made tool server for agents. Use the command line or the C library.
  • Aster tests Aster apps. It doesn't load web pages.
  • Images are PNG only. Aster is before 1.0, so names can change.