Skip to content

v1.3.3

Choose a tag to compare

@al2m4n al2m4n released this 19 Oct 21:50
35cb81e

TheYgent 1.3.3 is a patch release with two RAG fixes. Neither one limited how big a single document can be. That limit is the rag.max_upload_bytes setting: 50 MiB by default, up to 1 GiB, under Settings → RAG.

RAG: the document list no longer stops at 500 (#96)

A source's document list showed only its first 500 documents and dropped the rest without saying so. Ingest and search always used every document; only the list was cut short.

  • RAG page: click a source's name to see its documents, oldest first. A large source loads 100 at a time and shows "Showing X of N documents" with a Load more button.
  • API: GET /rag/sources/{id}/documents takes limit (1–500, default 500) and after, and returns next_after. Pass that value as after to get the next page; null means you have them all. An after that names no document of the source returns 400 invalid_rag_cursor. A call without these parameters gets the same first page as before, plus next_after.

MCP server: add_rag_files follows your upload limit (#96)

add_rag_files refused any file over 50 MiB, even after an admin had raised the limit. It now streams each file from disk, so a large file isn't held in the MCP server's memory, and lets the control plane enforce the limit. A file over the limit is skipped, and its result names the limit and where to raise it. The rest of the batch continues.

One call still indexes at most 500 files, and says so in its result.

Upgrading

  • No database migrations.
  • No changes to existing agents or their content hashes.
  • One additive API change: the paging parameters and the next_after field above. Existing callers keep working.

Full changelog: v1.3.2...v1.3.3