You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent transport and session-related bugs prompted fixes and additional fuzz and regression tests. The team wants to assess whether other parts of SLIM would benefit from similar coverage.
A release-pipeline blockage was resolved, and a new SLIM version was released shortly before the call.
The team discussed adding a pre-merge check so release-tool failures are visible before subsequent PRs accumulate.
2. Project Health & Dependencies
The team reviewed SLIM’s Linux Foundation/OpenSSF project-health score and the repository checks behind it, including scanning and vulnerability documentation.
An upstream dependency update is still needed for the cryptographic library used by SLIM’s MLS implementation. The issue is being tracked while the team monitors the upstream release.
3. SDKs & Agent Testing
A new test comparing peer-to-peer and SLIM messaging is blocked by a group-invitation issue in fire-and-forget mode. The fix is in SLIM core; an updated Go binding is needed to use it. A bindings release was expected shortly.
Tests using real LLMs have not yet produced a clear performance comparison because results vary between runs. The team is also testing a simulated task scenario and plans to coordinate on a more repeatable approach.
4. Agent Bridge & Shady
Work is progressing on discovering and composing agents through agent skills, exposing them through A2A servers, and testing collaboration with live agent harnesses.
Identity work aims to let receiving agents apply policies based on both user and agent identity, with revocation still under investigation.
Shadi has moved from derived keys to signed certificate chains for its human-to-agent identity model. An updated Shadi CLI release is planned now that WinGet distribution is available.
5. libp2p Transport Discussion
libp2p shared updates on WebTransport, AutoNAT, hole punching, and WebRTC Direct.
The discussion highlighted a practical distinction: QUIC-based transports may work within a private environment but can face restrictions when crossing enterprise network boundaries. HTTPS remains the current preference for broadly reachable discovery and authentication.
Next Steps & Action Items
Bindings: Release updated bindings containing the recent SLIM fix, then resume the blocked testing and downstream updates.
Release checks: Explore running release validation on PRs so dependency or release-tool issues are caught before merge.
Testing: Expand transport regression coverage and work toward more repeatable agent-comparison tests.
Agent Bridge: Continue discovery, identity-policy, revocation, and live-harness integration work; split the broad identity PR into smaller reviews.
Shadi: Publish an updated Shadi CLI package through WinGet.
libp2p: Follow up on enterprise-network compatibility when evaluating additional transports.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
SLIM Working Group Call Summary - Sept 29th, 2026
Key Topics & Outcomes
1. SLIM Fixes, Testing & Release Pipeline
Recent transport and session-related bugs prompted fixes and additional fuzz and regression tests. The team wants to assess whether other parts of SLIM would benefit from similar coverage.
A release-pipeline blockage was resolved, and a new SLIM version was released shortly before the call.
The team discussed adding a pre-merge check so release-tool failures are visible before subsequent PRs accumulate.
2. Project Health & Dependencies
The team reviewed SLIM’s Linux Foundation/OpenSSF project-health score and the repository checks behind it, including scanning and vulnerability documentation.
An upstream dependency update is still needed for the cryptographic library used by SLIM’s MLS implementation. The issue is being tracked while the team monitors the upstream release.
3. SDKs & Agent Testing
A new test comparing peer-to-peer and SLIM messaging is blocked by a group-invitation issue in fire-and-forget mode. The fix is in SLIM core; an updated Go binding is needed to use it. A bindings release was expected shortly.
Tests using real LLMs have not yet produced a clear performance comparison because results vary between runs. The team is also testing a simulated task scenario and plans to coordinate on a more repeatable approach.
4. Agent Bridge & Shady
Work is progressing on discovering and composing agents through agent skills, exposing them through A2A servers, and testing collaboration with live agent harnesses.
Identity work aims to let receiving agents apply policies based on both user and agent identity, with revocation still under investigation.
Shadi has moved from derived keys to signed certificate chains for its human-to-agent identity model. An updated Shadi CLI release is planned now that WinGet distribution is available.
5. libp2p Transport Discussion
libp2p shared updates on WebTransport, AutoNAT, hole punching, and WebRTC Direct.
The discussion highlighted a practical distinction: QUIC-based transports may work within a private environment but can face restrictions when crossing enterprise network boundaries. HTTPS remains the current preference for broadly reachable discovery and authentication.
Next Steps & Action Items
Bindings: Release updated bindings containing the recent SLIM fix, then resume the blocked testing and downstream updates.
Release checks: Explore running release validation on PRs so dependency or release-tool issues are caught before merge.
Testing: Expand transport regression coverage and work toward more repeatable agent-comparison tests.
Agent Bridge: Continue discovery, identity-policy, revocation, and live-harness integration work; split the broad identity PR into smaller reviews.
Shadi: Publish an updated Shadi CLI package through WinGet.
libp2p: Follow up on enterprise-network compatibility when evaluating additional transports.
All reactions