OpenHands v1.29.0

The change that matters in OpenHands 1.29.0 is spread across several separately listed features: on a local backend, every conversation now launches from an agent profile, and each profile carries its own settings instead of borrowing global ones. According to the commits in pull request #18720, the seeded profile called default now launches by its ID like any other profile, the older path that assembled settings inline is gone, and a local launch with no active profile fails with an error. The profile editor gains sections for choosing skills from the agent server's catalog, a condenser and verification settings, and a Model Router, each listed as its own feature in the notes.

For people upgrading, the practical effect is that settings move house. Each local backend runs a one-time migration that copies the old global behavior into default: the condenser, verification (except the critic API key, which stays global), tools, persona, system-message suffix, agent, tool concurrency, the Model Router and the Skills page selection. After that, the global Condenser page is removed and a direct link to it opens the Agents page, the Verification page keeps only the critic key, confirmation mode and security analyzer, and the Model Router page still defines routers but each profile picks its own. Deleting a router first detaches it from any profile using it, because a launch refuses a missing router. The Skills page now reads and writes default's list and seeds new profiles. OpenHands Cloud keeps its account-wide pages. Profile saves require agent-server 1.55.0, since older servers reject the new skills field with a 422 error (#18686), and the launchers now point the agent server at the bundled @openhands/extensions package rather than cloning the extensions repository at main (#18683).

The remaining fixes are smaller: chat now catches up with the model within a second instead of ten, and the uvx launcher is pinned to Python 3.12 through 3.14 until dependencies ship 3.15 wheels. The notes also repeat that the macOS desktop app is not yet signed with an Apple Developer ID, so macOS may report a downloaded build as damaged until the quarantine flag is cleared.