Skip to content

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 24 Oct 23:39
· 152 commits to main since this release
v0.2.0
89ee544

[0.2.0] - 2026-10-24

Added

  • Selectable MCP capability providers, including version-pinned binary servers
    with checksum-verified downloads and caching.
  • Hosts can pass surface_type and surface_id through build_runtime and
    supply extra context item builders to handle_message. Pack-provided items
    take precedence when item IDs collide.
  • End-to-end scenarios can declare surface identity and verify it through
    the harness.

Fixed

  • The stuck-in-stage guard counts only iterations in the current turn, not
    earlier conversation turns in the same workflow mode. New turns and operator
    resumes get a fresh stage budget; within-turn nudges and caps still apply.
  • Git subdirectory pack installs use the pack key for package-name policy
    checks, including URLs with multiple fragment parameters.
  • In-process memory server initialization uses the default backup retention
    when the shared argument namespace lacks backup_keep.

Changed

  • Catalog and authored-content adapters reuse long-lived stdio MCP sessions
    instead of starting a Python server for every call. Framework setup prewarms
    catalog and content concurrently; catalog invalidation also clears the
    persistent server cache. Sessions close at process exit and can be closed
    explicitly with close_shared_sessions().
  • A local startup profile measured catalog/content adapter time falling from
    approximately 24.8 seconds to 4.4 seconds. These are diagnostic observations,
    not an end-to-end latency guarantee; the model calls differed between runs.
  • Tracked follow-up: same-configuration framework rebuilds can retain
    cached authored text after files change. The
    prompt startup spec prioritizes refresh and
    runtime-owned teardown before further in-process startup optimization.
  • Memory provider bindings now live in pack MCP manifests instead of runtime
    aliases. Providers publish the stable memory.add, memory.search, and
    memory.list contract; additional memory tools are provider-dependent.

Upgrade notes

  • Upgrade the framework distributions and bundled packs together to 0.2.0,
    then restart the host. Hosts release separately; reinstalling an older
    framework version does not include the turn-budget fix.
  • Alternate memory providers must declare the memory capability and its
    required tools in their MCP manifest. Select the active provider with
    providers.capabilities.memory; runtime-specific memory aliases are gone.
    See the memory architecture.
  • New host context-builder and surface-identity parameters are optional.
    Existing callers can omit them.