Release 1.55.2

Canvas Code shows an iPhone inside the canvas itself, next to the code, with tap and keyboard. It is a panel many people like having. The problem was that it had become the answer to a question nobody asked.

Asking an agent to "run the app" got you a device booted inside the canvas, without having asked for it.

Why it happened

The agent only saw one door. The list of panels it can open offered the simulator, the tools for looking and tapping told it to open one, and nothing anywhere said that the usual home of an iOS app is the Xcode Simulator. A single door is not a choice: it is the path.

What changes

The default is now the Xcode Simulator, outside the canvas, with Xcode's debugger attached to it, as it has always been. The canvas panel is still there in full, and it comes in when you ask for the simulator in here.

The difference between the two is what each one costs. A browser page is content, and showing it in the canvas costs a panel. A simulator is a machine: booting one costs seconds, memory, and it stays up after you close the panel.

If you like the one inside

Settings › Simulator has the choice: In the Xcode Simulator or In a canvas panel. Pick the second and the agent opens the device here, every time, without you asking.

In both modes, asking for the other one works. The setting only decides what happens when you said nothing.