Chrome Extension on Programmer.ie: Modern AI programming

Build the Smallest Browser AI Observatory

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

We are ready to make the browser’s AI lifecycle visible.

The first version will be deliberately small. It will not inspect every page, intercept arbitrary prompts, call tools, diagnose quality or persist a history. It will do five things:

create a panel inside Chrome DevTools;
report whether the Prompt API is exposed and available;
create a browser-managed language-model session with visible download progress;
stream a prompt with cancellation;
display an event trace that separates each phase.

That is already more useful than a chat demo.

From Prompt Demo to AI Debugger

Wed, 02 Sep 2026 12:15:00 +0100

Our first DevTools panel can run a prompt and display its lifecycle.

That makes it a useful experiment console.

It does not yet make it a debugger.

A debugger must help explain a failure that occurred in the application under inspection. It needs to connect model activity to application context, preserve events long enough to compare them, and distinguish facts it observed from inferences it derived. It must do this without quietly capturing every prompt, response and page the user visits.

When Local Is Not Available

Wed, 02 Sep 2026 16:30:00 +0100

A browser-native AI feature cannot assume that its preferred local capability exists everywhere.

The API may be absent. Hardware may be ineligible. A language pair may be unsupported. Model assets may need acquisition. Session options may be rejected. Storage pressure or a browser update may change a state that worked yesterday.

Reliability begins by treating local availability as a runtime condition, not an installation promise.

1. Unavailable is not one state

A useful feature distinguishes: