opencode v2.2.6

The most consequential change in opencode v2.2.6, a release of the coding agent that has terminal, desktop and SDK interfaces, is how the scripted opencode run command finishes. It now waits for the background shell commands, subagents and image jobs that its prompt started, then lets the model respond to their results before exiting, printing a count of the jobs it is waiting for (or a background_wait event with JSON output). There is no time limit. A job that never exits, such as a dev server or file watcher, keeps the run open until someone presses Ctrl+C or sends SIGTERM, and the notes advise setting a timeout on CI jobs. SIGTERM now cancels the session and its background jobs and exits with code 143.

Two new flags are aimed at the same scripted use. With --archived, opencode run creates the session already archived, so scripted and CI runs stay out of the inbox, the home view and session lists, and --continue skips them. With -w, or --worktree= followed by a name of your choice, the run starts in a new git worktree, a separate checkout of the repository, so its edits do not land in the current working tree; it cannot be combined with --continue or --session.

The release also stops a file in a project from running scripts on the opencode server's web origin, the address a browser treats as the server's own. File reads and media from the server API are now served as sandboxed downloads, and cross-site browser navigations and requests from disallowed origins to its /api/ routes are refused. Web fetches now reject URLs that contain credentials, and Code Mode's fetch checks every redirect against the user's webfetch permission rules. The notes describe these fixes without saying whether the earlier behavior was ever exploited.