Repository navigation
Release v0.2.3
agent-application v0.2.3
Released 2026-10-26. A patch release. Since v0.2.2: generated Apps read only what the page shows, and the
agent's fallback model is gpt-6.1-sol. Private repository and image, docker.io/oramasearch/agent-application:v0.2.3.
This release is the tree of dev at ba264e5 with these notes, the version and the README's release line.
What it includes
| PR | Change |
|---|---|
| #52 | The prompt says to aggregate in SQL and page row-level reads with LIMIT/OFFSET, never SELECT * without LIMIT, and never to join whole tables in the App. unbounded_selects() flags a literal sql(...) statement with neither a LIMIT nor an aggregate, in validation and repair, naming the line (#51). The fallback model is gpt-6.1-sol |
| #50 | The v0.2.2 release merge |
Why:
- A production App copied three whole tables into memory every ten minutes.
- Lake v0.7.2 answers
too_many_rowsto an App query past 5,000 rows. - In Lake v0.7.2 people choose the agents' model per workspace (default
gpt-6.1-sol), and the gateway applies that
choice to this agent's calls. The fallback matters only when the agent is run without a Lake model.
Not included
- Apps already generated are not changed. One that reads whole tables is fixed by a
repairorchangeturn.
Known issues
As in v0.2.1.
Verification
| Proof | Result |
|---|---|
Full suite (uv run pytest) |
74 passed, 0 failed, 0 skipped |
| New test | the production loader is flagged; GROUP BY, an aggregate and LIMIT/OFFSET paging pass |
| Dev environment | agent-application:ba264e5 (this tree's code) ran on dev with lake dev-11153627, Ready |
| Image | built from the tag on the cluster BuildKit (linux/amd64) |