Sentence interface

Inflect

A sentence is not a prompt. It is the tool.

Inflect reads one written sentence and composes it into a working interface: the words stay, and the parts that describe a tool become the tool.

The build runs locally and deterministically. The same sentence always produces the same tool.

Form
Sentence interface · working build
Status
Working build · live demo
Year
2026
Inflect's working build: the sentence “coffee with rhea friday at 6pm” read as an event, with the parsed words highlighted in the sentence and carried into the tool as the date, time and person controls.
The working build: one sentence read as an event, with its own words turned into controls.

The idea

How one sentence becomes an interface.

Instead of asking a model for an answer, Inflect parses what you wrote into an interface. The nouns and times that describe the task become the controls; the rest of the sentence stays visible as the record of what was asked.

The interaction

Parsed words stay on screen.

In the build, the parsed parts of the sentence are marked in the sentence itself and mirrored as controls inside the tool: a date, a time, a person. Nothing is moved into a form field where it can no longer be checked.

Detail of the tool: the parsed date, time and person as controls beneath the sentence they were read from, with the save action below.
The date, the time and the person: the sentence's own words as controls.

The build

Local, deterministic, and published.

The build includes a set of example sentences (an event, a reminder, a calculation, a contact, a focus block, a split of an amount between people) and an inspect view of what the parser understood.

Input
One written sentence.
Output
A working tool built from the sentence's own words.
Runs
Locally and deterministically, with no model call.
Examples in the build
20 sentences, including an event, a reminder, a contact, a split and a choice.
Public surface
A live demo deployment, reachable from this page.

The live deployment is a public demo of the same build, not a separate product: authoring and parsing still run in the browser, and nothing is sent anywhere.