Skip to content

Releases: junit/open-agent-workflow

Open Agent Workflow v0.2.0

Choose a tag to compare

@junit junit released this 16 Aug 16:54

Open Agent Workflow v0.2.0

This release completes OAW's static, rule-driven Policy baseline across nine
Agent Hosts while keeping Bridge and machine evidence optional.

Highlights

  • Adds complete Policy Adapters for Claude, Codex, Gemini, OpenCode, Cursor,
    Windsurf, Cline, Roo, and Copilot.
  • Adds thin native entrypoints: $oaw for Codex and /oaw for the other eight
    Hosts, while preserving natural-language activation.
  • Tracks each Activation Router, native entrypoint, and Codex invocation-policy
    artifact independently through install, check, update, force, and uninstall.
  • Upgrades clean v0.1.x Install State to format 2 and atomically adds native
    artifacts for every previously installed target.
  • Adds rollback coverage that preserves concurrent replacement directories and
    foreign content.

Activation Safety

  • Native dispatchers require user-selection evidence originating outside the
    dispatcher artifact and Host-expanded template text.
  • Quoted or discussed invocation forms, automatic matching, model-led loading,
    and physical loading alone remain inert.
  • Dispatchers contain no Policy path, default Profile, duplicated lifecycle,
    approval gate, Skill choice, tool choice, or permission choice.

Boundaries

The installed Policy, selected Profile, independently installed Skills, and
Host-native abilities remain the complete operating path. Removing the oaw
binary, Bridge, or Machine Assurance does not disable normal Policy operation.
Static installation and dogfood validation do not claim live runtime E2E on
every Host.

See CHANGELOG.md in the release archive for the complete release record.

Open Agent Workflow v0.1.1

Choose a tag to compare

@junit junit released this 15 Aug 18:22

This release finalizes the static Policy product baseline.

  • Normal delivery remains rule-driven and fully usable without Bridge.
  • Default oaw checks Policy installation integrity and Host target readiness only; it does not determine Skill availability.
  • Provider scanning, cache probing, and exact Binding identity remain isolated in the optional Machine Assurance and Codex Bridge path.
  • Documentation and active architecture records now describe only the current product boundary.

Release archives include the default oaw executable for macOS, Linux, and Windows, plus the offline install wrapper and SHA256SUMS. Optional oaw-assurance and oaw-bridge remain separately built components.