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
Code Complete: All development work and feature PRs for SLIM v2.0 have been successfully merged into the main branch. This includes the final PR enabling browser WebSockets (with some minor compilation flag adjustments).
Documentation Finalization: The only remaining blocker for the v2.0 release is the massive documentation update. The team is currently incorporating the very latest features (added just last week) into the docs. Once this PR is merged, the official v2.0 release will be cut.
Post-Release Actions: Following the core release, the team will update all documentation links and roll out a new version of the language bindings to ensure everything is perfectly synced.
2. Community Blog PRs & Previews
A brief discussion was held regarding a technical limitation with GitHub Pages previews for community-submitted blog PRs.
Currently, PRs originating from external forks do not automatically generate a live preview due to security precautions. The team discussed workarounds, such as maintainers pulling the PR and building it locally, or pushing a manual commit to trigger the preview.
3. Shadi CLI: Secure Multi-Agent Execution
A deep-dive presentation was given on Shady (Secure Host for Agentic AI Dynamic Instantiation), a local sandbox runtime designed to securely execute and interconnect agentic harnesses (like Claude Code, Cursor, Copilot).
The Problem: While SLIM provides secure, encrypted transport between agents, it does not protect against malicious or compromised agents within a trusted group (e.g., prompt injections that trick an agent into deleting local files).
The Solution: Shady acts as a kernel-level jail outside of the agent's harness. It enforces strict policies (blocking destructive operations or connections to known malware IPs) that the agent cannot override.
Agent Bridge & Disaster Recovery: Shady includes an "Agent Bridge" application (built on A2A) to allow secure group collaboration. It also features a Git-backed disaster recovery system that takes snapshots of the agent's workspace, allowing users to instantly roll back any destructive actions.
Next Steps: The team is currently working on a desktop UI to make Shady accessible to non-technical users and finalizing a comprehensive security analysis of the codebase.
Next Steps & Action Items
V2.0 Documentation: Finalize and merge the comprehensive V2.0 documentation PR (including the WebSocket documentation).
SLIM v2.0 Release: Cut the official SLIM v2.0 release immediately following the documentation merge.
Bindings Update: Roll out a new version of the language bindings synced to the v2.0 core release.
Shadi UI: Continue development on the desktop graphical user interface for the Shady application.
libp2p Updates: Carry over the planned libp2p updates (peer discovery/NAT traversal) to the next working group call.
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.
Key Topics & Outcomes
1. SLIM v2.0 Release Status
Code Complete: All development work and feature PRs for SLIM v2.0 have been successfully merged into the main branch. This includes the final PR enabling browser WebSockets (with some minor compilation flag adjustments).
Documentation Finalization: The only remaining blocker for the v2.0 release is the massive documentation update. The team is currently incorporating the very latest features (added just last week) into the docs. Once this PR is merged, the official v2.0 release will be cut.
Post-Release Actions: Following the core release, the team will update all documentation links and roll out a new version of the language bindings to ensure everything is perfectly synced.
2. Community Blog PRs & Previews
A brief discussion was held regarding a technical limitation with GitHub Pages previews for community-submitted blog PRs.
Currently, PRs originating from external forks do not automatically generate a live preview due to security precautions. The team discussed workarounds, such as maintainers pulling the PR and building it locally, or pushing a manual commit to trigger the preview.
3. Shadi CLI: Secure Multi-Agent Execution
A deep-dive presentation was given on Shady (Secure Host for Agentic AI Dynamic Instantiation), a local sandbox runtime designed to securely execute and interconnect agentic harnesses (like Claude Code, Cursor, Copilot).
The Problem: While SLIM provides secure, encrypted transport between agents, it does not protect against malicious or compromised agents within a trusted group (e.g., prompt injections that trick an agent into deleting local files).
The Solution: Shady acts as a kernel-level jail outside of the agent's harness. It enforces strict policies (blocking destructive operations or connections to known malware IPs) that the agent cannot override.
Agent Bridge & Disaster Recovery: Shady includes an "Agent Bridge" application (built on A2A) to allow secure group collaboration. It also features a Git-backed disaster recovery system that takes snapshots of the agent's workspace, allowing users to instantly roll back any destructive actions.
Next Steps: The team is currently working on a desktop UI to make Shady accessible to non-technical users and finalizing a comprehensive security analysis of the codebase.
Next Steps & Action Items
V2.0 Documentation: Finalize and merge the comprehensive V2.0 documentation PR (including the WebSocket documentation).
SLIM v2.0 Release: Cut the official SLIM v2.0 release immediately following the documentation merge.
Bindings Update: Roll out a new version of the language bindings synced to the v2.0 core release.
Shadi UI: Continue development on the desktop graphical user interface for the Shady application.
libp2p Updates: Carry over the planned libp2p updates (peer discovery/NAT traversal) to the next working group call.
All reactions