Repository navigation
From running librarian on kagent with kagent's default model, and from asking what someone needs to see before putting it into the stack they already run.
A real run, on a build of what is released here. The full minute.
Fixed
- An agent that found its operation in a search made the body's field up. Among several APIs,
capabilitiessaid of an operation only that it takes a body, and a small model went straight on to the write with a field of its own (comment, where the API takestext): on kagent, 2 of 6 writes had the right body.write,write_planand the A2Awriteandplanskills now say where a body's fields are told, andcapabilitiesnames a body's first fields among several APIs too, wherever the whole answer has room for them: always for a few small APIs, and among large ones as before. 12 of 12. - An agent whose write was waiting ended its turn instead of waiting. Told only that
write_statuscan wait, it asked its user whether it should, about one run in five on kagent with the skill and eight in ten with only the tools. The answer to a write that waits now says the next step in so many words: callwrite_statuswithwait_seconds45, once, before answering. 12 of 12.
New
examples/kagent: ten minutes. librarian from the chart beside kagent on Agent Substrate, a demo API, and one Agent with librarian's tools and skill. An agent that holds no credentials reads, then asks for a change that you approve on a page. Run from an empty kind cluster on Kubernetes 1.37, as kagent's guide asks, and on 1.35 with its feature gates.examples/agentgateway: five minutes. librarian behind agentgateway with Docker: agents use the gateway's address for MCP and A2A, people use librarian's pages. It is the configuration the docs give and the weekly run tests, and a test keeps it so.- The docs show it running. A recording of the kagent example, light and dark, at the top of the README, in the guides and on the site. Nothing in it is re-enacted; pauses while the model thinks are cut, and the pages say so.
- For each stack: what you add, what to run, how it is tested. One table in the README, In the stack you already run, for any MCP client, any A2A client, LiteLLM, agentgateway, and kagent with Agent Substrate.
- How kagent support is tested, said plainly. What runs with every commit, what was run by hand, when and on which versions, and what has never been run on a cluster (integrations).
- The README's links work on PyPI. The package's page is the README, where forty links to files of the repository led nowhere. The release points them at GitHub, at the release's tag.
Upgrade
- No configuration changes are needed.
capabilitieswithoutapimay name what bodies hold."body": ["text", "seen?"]where it said"body": true, when the whole answer has room for it. The answer stays undercapabilities_max_bytes. On GitHub's API alone, a search answer for an agent that may write grows from 6.5 to 7.7 KB; answers without a query, and answers for agents that only read, are unchanged.- An agent told that its write waits is now told to wait once, for 45 seconds or
mcp_max_wait_secondsif that is less. Withmcp_max_wait_seconds: 0it is told to ask again later, as before. - The skill's text changed in two places. A kagent Agent takes it from this release's image by digest:
oci: ghcr.io/kultar/librarian@sha256:84a51695c96c34aad2dec16e092a02cd3dcefc5c31589b814fe148df0a596c1d,path: skills/librarian. An older one keeps working.
Checked on kagent 1.0.1 (Agent Substrate 1.0.0, Kubernetes 1.37.0) with its default model, through agentgateway v1.7.0, and by the five integration stacks. Not run on a cluster: Agent Substrate without kagent, and any managed Kubernetes.
