The ultrawide screen as a desk of windows. Each tool opens as a sheet that snaps to a grid, and an arrangement of sheets can be saved as a desk and switched as a tab. The first desk keeps Command on the left, one large window in the middle for showing things, and working windows on the right.
Draft for OtoWhat the app does, written in third person from its own docs, for Oto to rewrite. His reasons are the dashed slots.
[screen: Desk as it is now. Its windows show client sessions and unpublished posts, so it needs a staged desk]
[Oto: why the big screen became a desk, and which desks he keeps]
How it works
6 parts
01
Windows on a grid
Each tool opens as a sheet that snaps to a grid of 16 columns by 6 rows, from one square or a thin rail up to a full column, and detaches again. The grid is invisible at rest and shows when a sheet is picked up. Real tools load in the windows: dashboard pages, local tools, and hosted tools that allow it.
[screen: a desk of sheets on the grid, staged]
02
The bar
Across the top: the saved desks as tabs, a launcher key in the centre, and on the right the plan usage meters, the date and time, save and the theme switch. Desks are saved in the vault, with a copy on the device so a desk opens at once.
[screen: the bar, with desk names checked]
03
The launcher
A grid of app keys in the style of a Stream Deck, using the studio's own app icons. A key opens a tool as a window, starts a local tool's server if it is down, or opens a Mac app. The same launcher is its own Mac app, Deck, and an iPad home-screen app.
[screen: the launcher with its icons loaded]
04
Command and Sessions
Command sits in the left window, reshaped for a column, with its composer pinned to the bottom. The Sessions picker below shows pages of nine slots, each with the agent's name, portrait and status; a slot switches Command to that session.
[screen: Sessions on the Internal tab. Client slots show client names]
05
Sheets made for the Desk
Small windows written for it: Cards, the approvals queue one card at a time; Requests; Calendar; Runs, the health of scheduled jobs; Skills; Sketches; and widgets for pipeline, content output, model usage, income and subscriptions.
[screen: a desk of the clean sheets: Skills, Runs, Usage and Output]
06
The browser
A browser inside the desk with back, forward, an address bar that takes an address or a search, reload and Open in Safari. Links from the desk's own windows open here. Before framing a site it checks whether the site allows it, and says so if not.
How it connects
To the other apps
Command
The fixed left window; the Sessions picker sets which session it shows.
The Cards sheet shows the same cards as the Approvals page and Command's Queue.
Other tools
Hosted tools that allow framing open as windows; Mac apps open as apps.
What it runs on
The plain version
A single web page served by the same Node server on the Mac, made for a 3440 by 1440 ultrawide in the browser. Its windows are frames of other pages and tools. Saved desks are a JSON file in the vault. Light and dark themes.
I'm starting a new brand called The Agentic Operator.
It's a space to share what I'm learning around AI and agentic workflows. Builds, software, design and the future of work.