AGNTCY SDK — current goals

[adamtagscherer]

AGNTCY SDK — current goals

This post is the living source of truth for what the AGNTCY SDK team is
working on.

We will keep this post updated as priorities shift. Discussion and proposals
welcome in the thread below.

Repositories we own

• Agent Directory SDKs

  • agntcy/dir-sdk-python
  • agntcy/dir-sdk-javascript
  • agntcy/dir-mcp

• SLIM bindings and A2A transports

  • agntcy/slim-bindings
  • agntcy/slim-bindings-go
  • agntcy/slim-a2a-python
  • agntcy/slim-a2a-java
  • agntcy/slim-a2a-dotnet
  • agntcy/slim-a2a-go

Meetings and channels we participate in

Agntcy Discovery & Messaging

• Slack channel: https://agntcy.slack.com/ssb/redirect
• Zoom meeting: https://zoom-lfx.platform.linuxfoundation.org/meetings/agntcy?view=week

Agent 2 Agent

• Discord server: http://discord.gg/a2aprotocol
• Zoom meeting: https://zoom-lfx.platform.linuxfoundation.org/meetings/agent2agent?view=week

AAIF (Agentic AI Foundation)

• Communication link: https://github.com/aaif/technical-committee#communication
• Meeting link: https://github.com/aaif/technical-committee#working-groups

Goals

1. Stabilize and maintain the SDKs we own (Arpi)

Epic: agntcy/dir#1524
Focus on v1 of each SDK rather than expanding scope. The goal is a small,
solid surface in every language we support, kept in sync with upstream.

• Triage and burn down open issues across all SDK repos.
• Keep each SDK aligned with the current upstream API of Dir, SLIM, and OASF.
• Tighten release hygiene (versioning, changelogs, published packages).

2. AI Catalog and Agent Directory alignment (Adam)

Epic: agntcy/dir#1520
The AI Catalog and Agent Directory work is moving — slowly today, but with
real momentum behind it. Our goal is to position the AGNTCY open-source
stack as the interoperable, community-driven bridge between these ecosystems.

• Participate actively in the AI Catalog community meetings and feed input
  into the proposals.
• Identify the smallest set of changes in our SDKs / OASF SDK that lets
  third parties consume Dir-published agents through their own catalogs.

3. SLIM as a recognized A2A transport upstream (Jani)

Epic: agntcy/slim#1646
Make SLIM a peer to HTTP in the A2A ecosystem, not just an AGNTCY add-on.

• Engage with the A2A project community
  the same way we engage with AI Catalog: meetings, proposals, transport
  spec input.
• Contribute (or get referenced) into the upstream A2A docs and SDKs so
  SLIM is listed as a supported transport.
• Commit to keeping the slim-a2a-* transports in lockstep with A2A
  protocol evolution as a first-class maintenance obligation.

4. Move SLIM bindings to a new repo (Adam)

Issue: agntcy/slim#1661
The new repository is created, the bindings can be moved to it. https://github.com/agntcy/slim-bindings