Your contract is the tool
Each channel's view and commands become tools, described from your JSDoc and checked against your types. A command marked @confirm is put to the person before it is sent.
SwiftUI and Compose, for the web
A declarative UI toolkit: components that run once, a real layout engine with typed props, and a theme instead of CSS. The whole interface runs in a worker, so whatever your code computes, the frame still lands.
Every pixel above is drawn by Gesso into a single canvas element.
Built for agents
The channel contract you already wrote is the tool definition. An AI agent reads what your app holds, sends the commands it declares, and operates the screen as a screen reader would, with nothing more for you to write.
Each channel's view and commands become tools, described from your JSDoc and checked against your types. A command marked @confirm is put to the person before it is sent.
For what no channel covers, an agent reads the interface as an outline and presses, types and tabs through it, by the same path assistive technology takes.
Operating the interfaceEvery new project tells a coding agent the rules, the docs are published for models, and the dev server lets the agent drive the running app to check its own work.
For coding agentsWhat you get
Flex and grid with CSS's own semantics, typed lengths, and text that wraps, clamps and sits on a baseline. Every case is checked against Chrome, so a box is the size you expect.
Layout in fullLines break where Chrome breaks them in eight scripts, with colour emoji, right to left paragraphs and web fonts loaded inside the worker. Both renderers, same result.
How text worksInputs, overlays, tables, trees and media. Every one themed, keyboard operable, and announced to assistive technology without you doing anything.
Browse the libraryBuilt on Gesso
Three applications written with the framework, each picked because the DOM would struggle with it. Open one, then try to make it drop a frame.
A CPU made of logic gates, playing Pong on an LED matrix. Double-click into it, rewire it, scrub the waveforms, and the game keeps its frame.
A spreadsheet you would keep a budget in. Block the main thread for five seconds and the formula engine finishes recalculating behind the freeze.
A SQL workbench with a real code editor and a results grid that keeps scrolling while the next query runs.
The model
A state change writes one property on one node. There is nothing to memoise, no dependency array to keep honest, no view identity to reason about. Your component function runs once, so every closure in it is stable.
import { percent } from 'gesso-core';
import { Button } from 'gesso-components';
import { type ComponentContext, type Inputs, computed, input, internalState } from 'gesso-framework';
export function Counter(inputs: Inputs<{ label?: string }>, _context: ComponentContext) {
const label = input(inputs.label, 'Count'); // inputs are cells; this one has a default
const count = internalState(0);
const caption = computed(() => `${label.value}: ${count.value}`);
return (
<row gap={12} x="center" y="center" width={percent(100)} height={percent(100)}>
<text text={caption} textStyle="title" />
<Button label="Add one" onClick={() => count.value++} />
</row>
);
} Neither version names a colour. primary is a theme token, resolved when it is painted, which is why the counter follows this page's light and dark toggle.
The scaffold writes the worker, the shell and the first component, then gets out of the way.
$pnpm create:app my-app