See it in action

Screen recordings of the app. One capability per clip.

How these were recorded

For most of them, one window drove the other

An agent in window A sent each prompt over the local socket, then waited for window B to finish. The clips about the interface itself are clicked by hand, and say so under the video.

Window A · driving over the CLI

Send the prompt, wait for the pane to go idle.

nexion terminal send --window B "Draw this…"

nexion pane list --window Bworking

nexion pane list --window Bidle

Window B · the agent on camera
terminal
canvas

opened the pane, drew with MCP

Nobody taught it these commands. Nexion hands every agent that context when it starts.

iOS Simulator

It drives the phone, then hands you the shots

Home screen first. Then the agent opens the app in the simulator's browser, taps through the sign-in form, reads each field back before submitting, and attaches the booking list as it looks on the phone. Both shots land in the workspace, named after the device and the minute.

› Take a screenshot of the simulator home screen and attach it. Then open the app in the simulator's browser, sign in with the demo account shown on the page, and attach a screenshot of the booking list.

Played faster than real time

Browser

Signed in on one side, anonymous on the other

Two panes open on the same URL, one on your profile and one private. The agent signs in on the left, fills the booking form and submits it. The right pane never had the session, so it keeps showing what a stranger sees.

› Open http://localhost:8123/bookings below me twice, side by side: one normal and one private. Then sign in on the normal one with the demo account and add a booking, and tell me what the private pane shows afterwards.

Played faster than real time

Context

It already knows where it is

A fresh session in a project tab, nothing configured and no file opened. The agent answers with the commands this workspace hands it: attach a file to the card, split a canvas pane, notify the Mac, drive a browser or the iOS Simulator.

› What can you do in this workspace that you couldn't do in a plain terminal?

Played faster than real time

Browser

Reads the web without leaving the window

The agent opens a browser pane beside the terminal, loads the page, and summarises it while it is still on screen. Two things in one frame: the browser lives in the workspace, and the agent can read it.

› Open https://nexion.one beside me and tell me in three bullets what this product does.

Played faster than real time

Workspaces

Save a layout, bring it back running

Right click the tab, pick a saved workspace, activate it. The three panes come back in the same split and each one restarts what it was running: the agent, the mock build, a shell.

Played faster than real time. Clicked by hand, not driven from another Nexion window: this one is about the GUI.

Appearance

Changes the face of the workspace

One sentence, and the window goes dark: appearance, terminal theme, editor theme and the icons in the file tree. No preferences panel is opened, and the agent says which piece it had to set by hand.

› Switch the whole workspace to dark: window, terminal and editor. Use the Catppuccin Mocha icon pack.

Played faster than real time

Canvas

Ask for a diagram, get a file

A canvas pane opens beside the terminal, the architecture is drawn, and the file lands in the project as .excalidraw.

› Draw this project's architecture on a canvas beside me, top to bottom.

Played faster than real time

What should the next clip show?

Every clip here started as something we wanted to prove. If there is a thing you do every day across four apps, and you would like to see whether an agent can do it in one window, write and say so. The good ideas get filmed, and you get told when they are up.

[email protected]

More clips as they are recorded.

Download for macOS