feat: optional agentId in chat + agents.list() (v0.1.2)#9
Merged
Conversation
lgrosales
force-pushed
the
feat/sdk-resolve-agent-id
branch
from
a3823c7 to
5ac72a4
Compare
chat.send / chat.stream now accept calls without an agentId: the SDK resolves the single agent the credential is bound to via GET /api/agents (which returns only the bound agent for a credential caller) and caches it. register() returns the credential handle only, so callers no longer need an agent id for the common single-agent case. Add client.agents.list() and the Agent type. Pass agentId explicitly to target a specific agent, or when the credential can reach more than one (a multi-agent result throws RalioConfigError rather than guessing). Bump to 0.1.2; update README note + examples; add tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
lgrosales
force-pushed
the
feat/sdk-resolve-agent-id
branch
from
5ac72a4 to
564db69
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
chat.send/chat.streamno longer require anagentId. When omitted, the SDK resolves the single agent the credential is bound to and caches it, so the common single-agent case needs no agent ID.register()returns the credential handle only (no agent ID), so this removes a frequent point of confusion.Changes
chat.send/chat.stream:agentIdis now optional. When omitted, the SDK lists the caller's agents (GET /api/agents, which returns only the bound agent for a credential caller), uses the single result, and caches it. PassagentIdexplicitly to target a specific agent, or when the credential can reach more than one (a multi-agent result throwsRalioConfigErrorrather than guessing).client.agents.list()and the exportedAgenttype.0.1.1->0.1.2; CHANGELOG entry.lint/typecheck/test/buildall pass.🤖 Generated with Claude Code