A desk with room for the whole thought.

What is it?

A desktop workspace that arranges an editor, terminal, browser and other panels on a canvas.

What problem does it solve?

Editors, terminals and browser panels share an infinite local canvas.

What does it replace?

Potentially the window arrangement and context switching around a supported code editor.

What doesn’t it replace?

The underlying editor or every IDE. A local shell also does not make external AI services local.

Who is it for?

Developers who use spatial organisation to keep related work together.

The review notebook

A canvas is useful when position carries meaning: the terminal belongs beside this file; the reference belongs beside that browser. It is less useful when the map becomes another thing to maintain. Both outcomes are plausible here.

The proposed test is deliberately mundane. Open a real set of working panels, close the application and come back tomorrow. Does the arrangement survive, and can the keyboard still take you where you need to go? That will tell us more than an empty canvas screenshot.

Known catches & open questions

The README excludes WSL and limits embedded editors to supported VS Code-family applications. Binaries are described as unsigned.

Current judgement

This is a promising lead, not a recommendation. We will only make a hands-on judgement after the stated test has been run.

Next on the bench

Create a modest workspace, restart it, check state recovery and keyboard navigation, and record memory use with the same panels open.

Sources & evidence

Project repository and README ↗
Release history ↗

Public material checked 5 September 2026. Version labels are the latest stable release returned at that check, where available. Platform descriptions are upstream claims, not Toolglass acceptance tests.