Skip to content

Release v0.2.1

Choose a tag to compare

@homer6 homer6 released this 26 Oct 03:02
· 23 commits to main since this release
5f7bf2b

agent-ask-orama v0.2.1

Released 2026-10-25. A patch release. One change since v0.2.0: prompt v17, which
follows Lake's Quickstart after the person confirms a model (lake#1204). Private repository and image,
docker.io/oramasearch/agent-ask-orama:v0.2.1. Tracking issue:
#57.

It is a patch: no setting, route or turn shape changes for a caller. With an older Lake the turn
behaves as in v16.

This release is the tree of dev at 3c9685c (everything in the table below) with these notes, the
version and the README's release line.

What changed

Every pull request merged into dev since v0.2.0:

PR Change
#56 Prompt v17: follows the Quickstart after a confirm (says what started and what comes next, reads quickstart_status when asked about progress, proposes the corrected train_quickstart as a card after a failure, never tells the person to configure an engine setting). lake#1204
#55 Records the v0.2.0 image digest in the v0.2.0 notes
#54 Merges main back into dev after v0.2.0

Prompt v17: following the Quickstart after a confirm (#56)

On lake-dev, after Steve confirmed a clustering model, Ask Orama answered "Done: train_quickstart."
and, asked whether training had finished, told him to "configure the segmentation K range", which a
person cannot do. v17 is v16 plus Following the Quickstart after a confirm:

  • after a confirm, it says what started and what comes next, never "Done: train_quickstart";
  • asked about progress, it reads quickstart_status for the page's quickstart_id in the same turn;
  • after a failure (quickstart_state: failed, a failed proposal, or the person saying so), it says
    why in the person's words (model_problem) and proposes the corrected train_quickstart as a card;
  • it never tells the person to "configure" graph hints, a K range, a holdout or any engine setting.

quickstart_text reads Lake's new page keys (quickstart_state, model, model_problem,
quickstart_next) and gives the training, failed and done states their own direction. The deciding
state is unchanged. PROMPT_VERSION is v17; v14 to v16 stay in prompts/. See
docs/quickstart/.

Before it rolls: settings

No new setting. The settings of v0.2.0 still apply
(AGENT_SERVICE_TOKEN and LAKE_URL required, both rendered by the operator).

v17 needs the Lake that sends the Quickstart's state on each turn:
lake#1213, merged into lake's dev on 2026-10-25 and
not in a lake release yet (lake v0.7.0 does not have it). Against an older Lake the page carries no
quickstart_state and every Quickstart turn is treated as deciding, as in v16.

Not included

Unchanged from v0.2.0:

  • no conversation memory across restarts (conversations are in memory, bounded);
  • no explicit workspace ids on data-plane calls, and no idle backoff on the bus
    (#12);
  • no startup failure when AGENT_SERVICE_TOKEN is missing, and no per-service or per-launch
    authentication (#45);
  • no live eval results for prompts v12 to v17, and no live methodology_draft eval.

Known issues

Security-relevant first. All open at this tag.

  1. #45 (LSR-180, low): the service starts
    without a token, and the token is one shared credential, not per service or per launch.
  2. Lake-side findings that reach this agent, open in other repos:
    lake#922 (LSR-013),
    lake#985 (LSR-118),
    lake#989 (LSR-183),
    orama-operator#793 (LSR-044).
  3. #12: no explicit workspace_id on
    data-plane calls and delegations, and no idle backoff on the bus.
  4. #27: the draft's lock hashes are read
    from pypi.org, not confirmed reachable from the pod, and no live methodology_draft eval.
  5. #25,
    #23: the live evals have not run on
    v12 to v17, nor the count evals. v17 has not been run against a live Lake carrying lake#1213.
  6. lake#1191: outside the Quickstart, Ask Orama
    cannot find "the last-uploaded dataset", because list_datasets has no upload time.
  7. #3: models are listed by project id
    instead of project name.

Where it has run

The v0.2.1 tree has not run on the dev environment. At this tag the dev member of
lake-nonprod pins oramasearch/agent-ask-orama:7a044af (the v0.2.0 tree, prompt v16); no build of
#56 has been pinned there. Steve asked for the release on 2026-10-25 ("merge it all, cut releases,
push all to nonprod"
), together with the lake change it pairs with.

The image

Built from the tag v0.2.1 (5f7bf2b) on the cluster BuildKit with build-agent.sh (linux/amd64, the
repository's Dockerfile), then tagged :v0.2.1 on that digest without rebuilding:

docker.io/oramasearch/agent-ask-orama:5f7bf2b@sha256:577fe7778fa532e962d958f35cb5c8f00132c782e36ccd1c0e5cbb38a56f9301, also tagged :v0.2.1 (same digest). The Docker Hub
repository answers 404 anonymously (private).

It is not rolled anywhere yet: pinning it on an environment is a separate change to the operator's set
files, through dev, testing, staging and prod in order.

Verification

Proof Result
Test suite (uv run --frozen pytest -q -ra, macOS arm64, Python 3.12.11, release branch) 145 tests: 145 passed, 0 failed, 0 skipped. tests/test_agent.py 77 (3 new for v17), tests/test_turn_destinations.py 16, tests/test_conversations.py 13, tests/test_service_auth.py 13, tests/test_methodology_draft.py 7, tests/test_bus_backpressure.py 6, tests/test_conversation_owner.py 5, tests/test_lake_bus.py 5, tests/test_release.py 3 (the installed package is 0.2.1, these notes exist and are indexed, /healthz reports it with prompt v17)
Offline evals Run inside the test suite (a fake Lake and a scripted model); counted above
Live evals (ask-orama-evals) Not run on v17 (they need a live model, a person's Lake key and a Lake with lake#1213)
Linux image build (cluster BuildKit, from the tag) Built from v0.2.1 with build-agent.sh: oramasearch/agent-ask-orama:5f7bf2b, also :v0.2.1, sha256:577fe7778fa532e962d958f35cb5c8f00132c782e36ccd1c0e5cbb38a56f9301; private (404 anonymously)