Browser AI Observatory on Programmer.ie: Modern AI programming

One Runtime, Several Interfaces

Wed, 02 Sep 2026 14:00:00 +0100

The first Browser AI Observatory knew about one global object: LanguageModel.

That was enough to expose the common lifecycle. We could inspect availability, create a session, monitor model acquisition, stream output, cancel a request and record what happened.

Chrome also exposes narrower built-in AI capabilities. Instead of asking a general language-model session to perform an arbitrary task, an application can create a summarizer, writer, rewriter, proofreader, translator or language detector.

Summarization Is a Contract

Wed, 02 Sep 2026 14:05:00 +0100

Summarization looks like the ideal local AI feature.

The input is already in the browser. The desired output is smaller than the input. The task is useful for articles, documentation, conversations, reviews and support content. Sending the entire source to a remote provider can feel disproportionate when a browser-managed model can operate on the device.

So the implementation seems obvious:

const summarizer = await Summarizer.create();
const result = await summarizer.summarize(text);

The code is correct.

The feature is unspecified.

Writing, Rewriting and Proofreading Are Different Operations

Wed, 02 Sep 2026 14:10:00 +0100

Writer, Rewriter and Proofreader all accept text and return text-related results.

That surface similarity makes it tempting to place them behind one function:

const output = await improveText(input);

The name hides the most important property of the operation.

How much is it allowed to change?

A writer may create content that did not exist. A rewriter may change expression while preserving the underlying message. A proofreader should correct a bounded class of errors while leaving correct content alone.