v0.6.0

Features

• launch apps and see the ones Emma started (#58) by @tronschell
  • computer gains a launch_app action. Give it an app's name —
    Notepad, Calculator, Google Chrome, or the name list_apps prints
    — and Emma asks the user once, starts the installed app, returns its
    identity and PID, and grants control of that instance for the turn. It
    never takes a file path and resolves only against installed
    applications.
  • Apps that Emma itself started are visible again. Both native helpers
    now hide only Emma's own binaries — the helper, the process behind
    --blocked-pid, the emma, emma-host, emma-cli, emma-pty,
    emma-computer, emma-option-tap and emma-transcribe executables,
    and anything under the helper's or Emma's own directory. Process
    ancestry is no longer consulted, so an app opened from Emma's shell or
    by launch_app appears in list_apps and can be read and controlled.
  • The terminal tool now says not to start graphical apps from the
    shell: on Windows its job object kills the command's whole tree when the
    call returns, so a GUI app opened there dies immediately. Use
    launch_app. The job also carries JOB_OBJECT_LIMIT_BREAKAWAY_OK, so a
    child that deliberately asks to break away can.
  • docs/computer-use.md and docs/tools.md cover the new action, the
    resolution order on each platform, and the exclusion rule.

Fixes

• keep macOS-only window calls off Windows and let approvals lapse gracefully (#61) by @tronschell

  • Windows computer use no longer crashes on its first app read. The
    activity cursor overlay was calling a macOS-only window method, which
    killed every get_app_state on Windows with setHiddenInMissionControl is not a function.
  • Models can find launch_app again. The tool description the harness
    advertises had never been updated for it and still told the model to ask
    you to open an app it could not see, so models started apps from the
    terminal instead — where the shell kills them the moment the command
    returns.
  • An app approval you did not get to in time is no longer treated as a
    refusal. Emma tells the model there is no answer yet and lets it ask
    once more; only Don't, Escape or a stop bans an app for the rest of
    the turn.

  🤖 Generated with Claude Code

Other changes

• release 0.4.0 (#30) by @tronschell

• install and launch both packages on the runners (#54) by @tronschell

  • CI now installs and launches both the macOS disk image and the Windows
    Squirrel installer on the runners, drives the installed app over the
    DevTools protocol to prove the workspace renders, uploads a screenshot
    of it, and uninstalls the Windows build again, so a broken package fails
    the build instead of reaching a release.
  • ci accepts a manual dispatch with a package input that runs the
    macOS and Windows packaging jobs, with the install smoke test, against
    any branch.

  🤖 Generated with Claude Code

  ---

• bump to 0.6.0 (#59) by @tronschell
  Emma 0.6.0 ships Windows x64 alongside macOS: a Squirrel installer with
  auto-update, PowerShell as the shell the model targets, computer use
  with app launching, durable terminal sessions, a taskbar and installer
  identity of its own, and zvec-grep downloaded on demand instead of
  bundled, which shrinks the Windows installer from 570 MB to 143 MB.
  macOS is unchanged in behavior and gains the same on-demand zvec-grep
  and the credential-store hardening.

  🤖 Generated with Claude Code

Full changelog: zvec-grep-v0.2.1…8904954