Replies: 1 comment
SLIM Working Group Agenda – June 2, 20261. Opening & ObjectivesWelcome and brief recap of last week's key outcomes. 2. Engineering Updates & Status ChecksBindings Migration to Dedicated Repo: Status update on completing the extraction of language bindings to the new repository to stabilize and speed up the CI pipeline. 3. Open Discussion & Next StepsRoundtable: Progress updates and blockers across contributors. |
Uh oh!
There was an error while loading. Please reload this page.
SLIM Working Group Call Summary – May 26, 2026
Participants (11): Nick Gill, Benjamin Torres, Kleyer Sosa, John Patten, Michele Papalini, Sam Betts, Mark Marton, Mauro Sardara, László Puskás, János Sarusi-Kis, Luca Muscariello.
Key Topics & Outcomes
1. SLIM v2.0 Milestone Progress & Breaking Changes
Development is officially underway for SLIM 2.0, which will introduce several non-backward-compatible changes (nodes and bindings will need to run the same major version).
Merged Features: The splitting of channels (separating control and data sub-channels) and the new control plane (rewritten in Rust) have been merged into the main branch.
Upcoming Changes:
Integrity Checks: Adding data plane integrity checks between nodes.
Global IDs: Moving agent IDs from 64-bit to 128-bit to ensure global-scale uniqueness. This will require slight API changes for routing commands.
2. Performance Optimizations
The team identified and resolved a significant performance quirk related to async_traits. The previous implementation was wrapping futures in a Box, causing an unnecessary heap allocation on every single function call.
Current optimization efforts are focused heavily on the "unreliable" messaging mode first. Once that is fully optimized, the team will shift focus to resolving bottlenecks in the "reliable" mode.
3. WebSockets & WebAssembly (Wasm)
Native WebSocket support has been successfully merged. SLIM nodes can now connect via gRPC or WebSockets.
The next major step is compiling the SLIM data plane to WebAssembly (Wasm) to enable full WebSocket client support directly within the browser.
4. A2A Custom Protocol Bindings
SLIM RPC: The initial specification for the SLIM RPC experimental binding has been merged into the new A2A custom protocol bindings repository. It includes comprehensive documentation on SLIM networking, method mapping, and error mapping (correcting previous gRPC status code mismatches).
Multicast RPC: A follow-up PR detailing the Multicast SLIM RPC specification is currently under review.
WebSockets: A draft proposal for the A2A WebSocket custom protocol binding has been submitted and is undergoing architectural review.
5. Repository Migration Status
The migration of language bindings out of the main SLIM monorepo into a dedicated repository is actively in progress. This move is expected to significantly speed up CI build times and reduce merge conflicts.
6. Community Introductions & Ecosystem Integrations
Security Integration: A new community contributor introduced a startup focusing on multi-agent system security. They are building a verifier for A2A channels to check policy correctness, block malicious prompts, and escalate to human review, and are looking to integrate this policy engine securely over SLIM.
GitHub EMU Bug: The team discussed an ongoing GitHub bug where issues created by Enterprise Managed User (EMU) accounts are completely invisible to repository maintainers. As a workaround, partners are emailing markdown files so maintainers can manually recreate the issues.
Next Steps & Action Items
Repository Migration: Complete the extraction of language bindings to the new repository to stabilize and speed up the CI pipeline.
A2A Protocol Bindings: Review and merge the Multicast SLIM RPC specification PR. Continue reviewing the A2A WebSocket protocol binding proposal.
Wasm Compilation: Begin work on compiling the SLIM data plane to WebAssembly to unlock in-browser WebSocket clients.
SLIM v2.0 Development: Finalize and merge the 128-bit ID migration and data plane integrity checks.
All reactions