Skip to content

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 23 May 07:29
· 58 commits to main since this release
v0.5.0 — align with aicodebox v0.4.0 /run payload restructure

This release tracks the breaking /run response restructure introduced
by aicodebox v0.4.0. Each ``outputFormat`` now produces one
well-defined surface:

  text          → {..., text}
  json          → {..., parsed} on success;
                  {..., text, parseError, jsonRetries} on failure
                  (up to 3 self-correction retries handled by the base)
  json-verbose  → {..., events}   (decoded pi NDJSON event stream)

Other base-layer shifts that surface in pibox responses
- Raw stdout/stderr are opt-in via ``includeRaw: true``. Default
  responses omit them. ``stderr`` is still auto-included on non-zero
  exit so failed runs remain diagnosable when text is empty.
- json-verbose × jsonSchema is rejected at the base; the adapter no
  longer owns that check.

PiAdapter
- validate() delegates output_format vocab + json-verbose × jsonSchema
  mutex to the base.
- parse_output() returns just text/session_id/usage. Envelope assembly
  is gone — the base now exposes events via the new parse_events()
  hook, which the adapter overrides to JSON-decode pi's NDJSON.
- parse_stream_event() unchanged — OAI streaming continues to emit
  per-token deltas.

Breaking changes for callers of /run
- json-verbose: read .events (list of decoded pi events) instead of
  the old .parsed envelope.
- json: success surface is .parsed only — the raw JSON string no
  longer ships in .text on a clean parse.
- All modes: .stdout / .stderr require ``includeRaw: true`` now.

The /v1/chat/completions surface (the OpenAI-compat client path) is
unchanged.

Built against psyb0t/aicodebox:latest (aicodebox v0.4.0+). Older base
images are incompatible — the new adapter relies on the base's
output_format vocab, retry loop, and includeRaw flag.