Repository navigation
Release v0.2.0
agent-application v0.2.0
Released 2026-10-25. A minor release. Six pull requests since v0.1.0, most of them
fixes from the 2026-10-21 security review: the service token is compared in constant time and turns
are refused when it is unset, a turn's credential goes only to the service's own LAKE_URL, and no
turn trace is kept on the pod's disk. It also proposes Lake's secret references and takes the Lake's
AGENT_MODEL. Private repository and image, docker.io/oramasearch/agent-application:v0.2.0.
This release is the tree of dev at 32caa4c with these notes and the version. Tracking issue:
#35.
How it works: service and bus operation,
building, confirming and deploying Apps, evaluation scenarios.
What it includes
Every pull request merged into dev since v0.1.0:
| PR | Change |
|---|---|
| #29 | POST /v1/turn compares the bearer with hmac.compare_digest, and fails closed: with AGENT_SERVICE_TOKEN unset or empty every turn is refused with 503 (it used to be open). A wrong or missing bearer is still 401 (#23) |
| #31 | A turn's credential goes only to Lake at this service's own LAKE_URL, for capabilities and the model gateway alike. The turn's lake_url is ignored. LAKE_URL must be an absolute http(s) URL with a host and no user info, query or fragment; otherwise, or when unset, the turn is refused before any request goes out (#30) |
| #27 | A turn keeps nothing on the pod's disk: no <TRACE_DIR>/<trace_id>.json. TRACE_DIR is no longer read; the answer still carries trace_id. Lake keeps the answer in the task's sealed record in the workspace Zetta (#21) |
| #28 | A secret environment value must be one of Lake's two reference forms, {"secret": {"mount_id", "name", "field"}} or {"secret": "lake-secret://<mount id>/<name>#<field>"}. A Kubernetes Secret name is refused. The prompt (still v1) proposes a reference only when the person named an existing secret, and otherwise leaves the variable out and points to the App's Environment settings (#19) |
| #32 | The model is APPLICATION_AGENT_MODEL when set, else the Lake's AGENT_MODEL, else gpt-5.5, so the Lake's spec.agents.model now reaches this agent (#22) |
| #26 | Records the v0.1.0 image digest in the v0.1.0 notes |
Settings it needs
| Variable | Why | Who sets it |
|---|---|---|
AGENT_SERVICE_TOKEN |
Now required: without it every POST /v1/turn is 503 (#29). Bus turns do not use it |
The operator, on every library agent pod |
LAKE_URL |
Now required for every turn, and must be a clean absolute http(s) URL (#31) | The operator |
AGENT_MODEL |
Now read (#32); APPLICATION_AGENT_MODEL still overrides it |
The operator, from spec.agents.model |
No new setting. The operator still sets TRACE_DIR=/tmp/traces; the agent ignores it. A hand-run
service must now set AGENT_SERVICE_TOKEN and LAKE_URL.
What it does not include
Unchanged from v0.1.0, except that turn traces are gone:
- no conversation memory that survives the process;
prior_turnis not read; - no explicit
workspace_idon its calls; - no creating secrets;
- no frameworks beyond FastAPI, Streamlit and static sites;
- no idle backoff on the bus;
- no live eval result: the live evals need a live model and were not run.
Known issues
Security-relevant first. All open at this tag.
- Library agents hold live task credentials for every tenant they serve
(lake#871): one shared process claims tasks for
every person, each with a credential that acts as that person. A design issue on Lake's side. - The bus consumer claims tasks into an unbounded queue before a worker is free
(#33, LSR-075): claimed tasks wait in
the executor holding their credentials. - Conversation histories are unbounded
(#34, LSR-076): they are never evicted
from the process's memory. - A confirmed turn cannot create an App with a Lake secret reference
(lake#891): Lake checks a reference with the
caller'sget_secret_mountandread_secret, which a confirmed turn's task credential lacks. The
agent now proposes the right form (#28); creating the App with it waits on Lake. - Confirmation gates do not establish a separate human confirmer
(lake#989, LSR-183, low). - A repository with the same name in another workspace makes the deploy fail with a conflict
(#18). - No explicit workspace IDs, and no idle backoff on the bus
(#3). - Lake's e2e T11 and T12 confirm without
proposal_task_idandproposal_sha256, so Lake refuses
the confirming turn (lake#1183). The script is
out of date, not this agent; until it is fixed the e2e gate does not exercise the confirm step. - The model is offered reads a design turn cannot make:
build_logs,get_buildand
receive_build_eventscome back as errors on a design turn.
Where it has run
The v0.2.0 tree has not run on the dev environment. No dev-<sha> build of these changes was
pinned on the dev member of lake-nonprod; every Lake runs the operator default,
oramasearch/agent-application:v0.1.0 (orama-operator internal/controller/lake_defaults.go on dev).
Moving the default to :v0.2.0 is a separate operator change, rolled through testing, staging and prod.
The image
Built from the tag v0.2.0 (8a10773) on the cluster BuildKit with build-agent.sh (linux/amd64, the repository's Dockerfile), then tagged :v0.2.0 on that digest without rebuilding:
docker.io/oramasearch/agent-application:8a10773@sha256:120a208d38e4655e31e54afcb1dcef06faf6f999cae0e36e5ac4a44e5d3f6982, also tagged :v0.2.0 (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) |
62 tests: 62 passed, 0 failed, 0 skipped. test_agent.py 21, test_service_auth.py 13 (new, #29), test_turn_destinations.py 10 (new, #31), test_service.py 7, test_release.py 3 (the installed package is 0.2.0, these notes exist and are indexed), test_evals.py 3, test_generated_apps.py 3 (generated Apps loaded by app-runtime at 692faac), test_lake_bus.py 2 |
| Release test | tests/test_release.py reads the version from pyproject.toml and the installed package, and fails when docs/releases/v<version>.md or its index line is missing |
/healthz version |
test_healthz_reports_the_release_version: version is the installed package's version |
Live model evals (application-agent-evals) |
Not run (needs a live model) |
| Linux image build (cluster BuildKit, from the tag) | Built from v0.2.0 with build-agent.sh: oramasearch/agent-application:8a10773, also :v0.2.0, sha256:120a208d38e4655e31e54afcb1dcef06faf6f999cae0e36e5ac4a44e5d3f6982; private (404 anonymously) |