New feature: remote execution targets

Main Event

• Execution Targets - We now treat laptops, SSH servers, VMs, containers, devboxes, and future hosted runners as the same concept: an execution target. Users can define local repository paths ("resources") for each execution target so that Overlord automatically launches agents in the correct place regardless of device. Each execution target simply needs the CLI installed and authenticated.
• Execution location switching — The ability to change the current target execution directory directly from the web and desktop interfaces.
• Project linking command — Overlord automatically saves a device fingerprint when an Overlord operation first runs on that execution target (device, VM, etc.), but users can now add a device directly using a new CLI command to interactively link your current working directory to a project.

Also Added

• Native browser notifications — Web-only users now receive OS-level notifications for agent alerts and updates.
• Custom launch commands (Beta) — Users can now prepend additional commands to agent launch commands, allowing integration with tools like custom execution containers (claude-pod) and other kinds of wrappers (ollama). You can find these in the "Local agent configuration" section of the CLI & Local Agents page in Settings.

Improved

• Unified notification system — Agent alerts and audio cues are now consistently delivered across desktop, web, and mobile platforms.
• Automatic CLI session persistence — The CLI now caches session keys locally, eliminating the need to manually pass session flags for every command.
• Streamlined project discovery — Standardized how projects are identified across all interfaces for more reliable tool performance.
• Flexible attachments — Relaxed strict requirements for linking files to objectives when the context can be automatically determined.

Fixed

• Real-time board sync — Fixed issues where the ticket board would fail to update automatically as work progressed.
• Duplicate session closures — Corrected a logic error that caused agent sessions to be terminated multiple times.