Skip to content

feat: accept agent_instance identities - #24

Merged
vitramir merged 1 commit into
mainfrom
t3/agent-instance-identities
Jul 31, 2026
Merged

vitramir merged 1 commit into
mainfrom
t3/agent-instance-identities

Conversation

@vitramir

Copy link
Copy Markdown
Contributor

Agent workloads authenticate as their instance (ziti-management now registers them as IDENTITY_TYPE_AGENT_INSTANCE), so tracing rejected every trace export from one:

  • Resolver.Resolve failed with identity type is not agent
  • where a span carried a message id, IdentityTypeMetadataValue failed first with unsupported identity type

Both paths now accept the instance type alongside the class. Nothing downstream needed changing — the agents service already resolves either an agent id or an instance id to the same agent and organization, and threads already accepts agent_instance as a participant type.

Identities minted before instances existed still present the class type and keep working.

Agent workloads authenticate as their instance, so every trace export
from one was rejected with "identity type is not agent" and, where the
span carried a message id, verification failed before that with an
unsupported-identity-type error.

Both paths now accept the instance type alongside the class. The agents
service already resolves either to the same agent and organization, and
threads already accepts agent_instance as a participant type.
@vitramir
vitramir merged commit a54fba6 into main Jul 31, 2026
1 check passed
@vitramir
vitramir deleted the t3/agent-instance-identities branch July 31, 2026 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant