Slack's agent tooling matures as the SDKs converge on sessions

Agent sessions arrive across the Slack SDKs

Slack spent the week building out the plumbing for agent-driven workflows, and both official SDKs landed the same capabilities in parallel. The Node SDK's web-api client gained methods for inspecting and steering agent sessions — admin.users.getExpiration, plus agents.sessions.rename and agents.sessions.setStatus, and a session_status field on chat.stopStream. The types package added the matching events for agent_session_stopped and agent_session_title_changed, so consumers can react when a session ends or gets renamed. On the Python side, the typed model classes for TableBlock cells and column settings fill in a gap that had forced developers to hand-roll block payloads.

The two SDKs also converged on richer input: Node's RichTextInput element now accepts optional min_lines and max_lines properties, and Python shipped the equivalent min_lines/max_lines support for RichTextInputElement. Python additionally introduced a stateless OAuth state store backed by JWT, which removes the need to persist session state server-side when you're running OAuth flows across multiple instances.

A socket leak and a duplicate-run bug in the Node SDK

The Node SDK's socket-mode transport had a real operational bug worth upgrading for: moving to undici's WebSocket had dropped the force-close paths, so disconnected clients left ESTABLISHED TCP sockets behind that accumulated toward Slack's per-app connection cap. The fix arms a 30-second close-handshake timeout so a peer that never answers the close frame can't strand a socket in CLOSING. Separately, the webhook client stopped retrying after a successful delivery: a 2xx response with an empty or non-JSON body used to throw a parse error that got retried as a request failure, silently firing Workflow Builder runs twice. Those bodies now resolve to { ok: true }, while genuine { ok: false, error } payloads still surface to the caller.

The SDK also walked back an internal packaging change: both web-api and webhook reverted to requiring ESM loading only where it's needed, restoring backward compatibility for CommonJS consumers.

Figma's agent panel breaks out of the window

Figma's desktop app now lets you pop the agent chat panel into its own window on macOS and Windows, so it stays visible while you switch tabs or work in another tool — a small change that matters if you're running an agent alongside a design file rather than inside it.

Routine maintenance

Notion shipped two bug-fix and performance releases this week with no feature changes to report, and Slack's desktop client had a quiet week by its own admission.