Anyone working on Kagent + AX?

[marcellodesales]

We've been building on top of Substrate and Kagent, so I want to see if there's any work on that direction...

[rakyll]

I'm interested in how the Kagent stack might layer with AX. Are there any active explorations, examples, or anything else we can look at?

[karimad]

Yes — actively exploring this exact combination (Agent Substrate + ax + kagent).

A few concrete, verified findings so far:

• kagent 0.10.1 installed and live-verified on a local kind cluster via the published OCI Helm chart. Note: the real released CRDs are Agent.spec.byo.deployment — an initial assumption based on main-branch API shapes (Harness/AgentTemplate/AgentInstance v1alpha3) turned out to be wrong.
• Built and live-verified a workload-identity (IRSA-style) credential path for ax Tasks: Agent Substrate mints a real per-actor OIDC JWT (MintActorJWT) and projects it into a Task's guest filesystem via a SystemInfoVolume entry. Verified end-to-end against a LocalStack IAM/STS instance — real JWT, exchanged via sts:AssumeRoleWithWebIdentity, real AWS-shaped temporary credentials returned.
• While closing the JWKS gap needed for that flow, found the key-management infra already existed (internal/localjwtauthority.Pool.VerificationKeys()) — only the HTTP-serving layer was missing. Before opening anything, checked upstream and found both halves already tracked: agent-substrate/substrate#1756 (JWKS/OIDC discovery, P0, assigned — with an agreed design of a separate ate-oidc-server rather than a listener on ate-api-server) and #1114 (an open PR for the atelet-projection mechanism, unreviewed for a month). Deferred to those rather than duplicating.

Caveat: none of the above is upstreamed — it's a local proof-of-concept in untracked clones, not a production-ready feature. Happy to share more detail if useful.

[ktsoator]

This sounds interesting! Could you share how you envision Kagent and AX working together—would agents run inside AX Tasks, or delegate isolated work to them?

[karimad]

In my testing, kagent was the orchestrator layer where the agent is hosted and ax is the sandboxed env where the risky task is done
so only delegates to ax when the task is calling AWS bedrock or dealing with credentials

[ktsoator]

Thanks for clarifying!

[marcellodesales]

I use Kagent as the orchestrator as well, where ALL agents talk A2A to each other... The intent of AX for is where a fleet of dynamic Agents must be created alongside our MCP broker whose credentials are minted... Thank you for all the inputs, we definitely will learn more along the way