If you installed v1.6.0 and your terminal kept insisting that Frontier was not there, you were not imagining it. The app was running. The server was listening. But the small program that lets Claude Code talk to it was packaged without the libraries it needs, so it gave up the moment it was asked to say hello.
The cause was a quiet rule inside the tool that assembles our installers: it leaves out a folder of dependencies by default, and it does so without a word. We have told it otherwise, checked the result the same way the tool itself does, and written the rule down where the next person will find it.
Install it, and the handshake works again on its own. Nothing to re-run, nothing to reconfigure.
One more thing, since we were in there. The examples on the website each end in a Try it button, and until now that button quietly built the example in a context of its own. Tidy, but presumptuous. Now Frontier asks first. Keep it separate in a fresh context, or drop it in beside the workspaces you already have and see how the two fit together. Everything an example creates stays marked as an example, and its agents stay off until you decide otherwise.