Skip to content

strike v0.5.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Aug 20:39
· 119 commits to main since this release
v0.5.0
f62c7bf

Install

curl -fsSL https://strike.jonathanung.ca/install | bash

Or download an archive below, verify checksums.txt, and place strike on your PATH.

Changelog

Minor release: Agent Plugins 1.0.0, a leaner default OS sandbox, --auto
vs --dangerously-skip-permissions, and web cockpit TUI-parity polish.

Added

  • strike plugin migrate — convert a legacy Strike-native bundle to Agent Plugins 1.0.0 (plugin.json, portable skills/ + mcp.json, Strike-only files under com.strike.cli/). Atomic: stage, validate, then replace. Installed plugins require --yes; digest is recomputed and trust is cleared (not auto-granted). --dry-run prints the plan. Already-APS packages are refused (#1145).
  • Agent Plugins 1.0.0 load path — install and run APS packages (plugin.json, skills/, mcp.json) plus Strike-only com.strike.cli extensions; CLI, catalog, doctor, TUI, and conformance tests follow the same contract (#1141–#1148).
  • Web cockpit TUI parity — composer autocomplete (arrows + top-down list), plugin panes docked beside Chat, Chat session-group inspector, and inspector/completion chrome aligned with the TUI (#1140, #1155, #1156).

Changed

  • Default OS sandbox is leaner — workspace-write still keeps $HOME and
    ~/.strike/config read-only, but now allows the toolchain/XDG caches and
    Strike session dirs coding workflows actually need. macOS Seatbelt grants
    file-map-executable, process-info, local IPC, and tty ioctls; Linux bwrap
    re-binds the host /dev/tty. Two strike processes (or a nested launch
    from sandboxed bash) can start without turning isolation off.
  • --auto vs --dangerously-skip-permissions — they are no longer aliases. Both still skip configured permission asks (agent denies remain). Only --dangerously-skip-permissions bypasses network.allow (bash preflight, webfetch, websearch). --auto keeps the allowlist. OS sandbox is unchanged for both. Eval runners stay on --auto so isolation still holds.
  • Plugin contract — native on-disk format is Agent Plugins 1.0.0 (plugin.json, portable skills/ + mcp.json). Strike-only assets use com.strike.cli. See docs/plugins.md (#1142).
  • Upgrade note: Agent Plugins is native. Strike-native plugin manifests (schemaVersion + contributions) are deprecated; removal is planned for a future major. Use strike plugin migrate. strike plugin install of a Strike-native tree fails unless --legacy is passed. Already-installed legacy packages continue to load (#1147).

Deprecated

  • Strike-native plugin authoring (schemaVersion + contributions + plugin.jsonc). Installed legacy bundles still load with a deprecation diagnostic until a future major. New installs require strike plugin install --legacy (#1147).

Fixed

  • Second strike binary failing to launch — the default macOS Seatbelt
    profile allowed process-exec but not file-map-executable / process-info /
    host tty, so a second Go binary (or nested strike from sandboxed bash)
    could not start. The availability probe now uses those primitives and runs
    in its own process group so a nested Seatbelt failure cannot signal the
    parent instance.

Full changelog: v0.4.0...v0.5.0

Assets 7
Loading