Skip to content
DreadnodeDreadnodeDreadnode

September 17, 2026

Workflows are now in open beta

← All updates

Workflows are now in open beta

6 new5 improved11 fixed

Workflows enter open beta this week, bringing multi-step agent pipelines to the CLI, SDK, and UI — alongside Slack integration, a runtime capability health tool for agents, and a redesigned org navigation shell.

New

  • Workflows. Define, run, and inspect multi-step agent pipelines from the CLI, SDK, and a new Workflows section in the UI — now open to all organizations in beta, with project-scoped catalog, stable graphs, inline CLI guide, and model selection at run time.
  • Slack integration. Org owners connect a workspace via Settings → Integrations, then @mention the agent to stream a full session in-thread — with stop support and a direct link back to the session in Agents → Sessions.
  • Agent runtime capability health tool. Agents can now call a built-in runtime_info tool to inspect which capabilities are loaded, enabled, and healthy in their runtime — including failed loads and component health — without raw config or credentials exposed.
  • Memory creation from the UI. You can now create memories directly from the Memories page using a new creation panel and form.
  • AI red-teaming targets documentation restructured. Custom HTTP targets, AWS SageMaker, and Azure AI Foundry pages are rewritten with verified examples, and the AWS and Azure multi-agent pages are consolidated into a single cloud-agnostic guide.
  • Organization avatars. Organization owners can now set an avatar in Settings — choose one of five color presets, upload a PNG, JPEG, or SVG, or fall back to the org name initial. The avatar appears everywhere the organization is shown.

Improvements

  • Chat runtime health inspector. Chat now shows a dedicated runtime health panel with grouped failures, per-component recovery actions, and copyable diagnostics — separate from the capability picker — with stable status updates that no longer flicker or lose expanded state.
  • Agent Output empty and error states. Agent Output now shows clear empty and error states for new projects, empty types, empty sessions, and load failures — each with a concrete next action instead of a dead end.
  • Platform version in account settings. The platform version is now visible in your account settings.
  • Workflows catalog empty state and onboarding. The Workflows catalog page has a consistent empty state, loading and error handling, an inline CLI guide, and a copyable run command on the definition page that includes the required project ID.
  • Hub browse order stabilized. Hub browse pages (Capabilities, Models, Datasets, Environments) now sort by creation date consistently, and pagination no longer skips or duplicates items when multiple artifacts share a sort value.

Fixes

  • Runtime resolved by owner, not list position. Runtimes are now resolved by owner across all project surfaces, so you always connect to your own runtime rather than a teammate’s.
  • Agent terminal errors now reported as failures. Agent turns that end with an error — including finish_task(success=False) and give_up_on_task — are now correctly reported as failures instead of successful completions in chat, workflows, and evaluations.
  • AIRT tools correctly registered. The provision_environment and generate_agentic_suite_attack tools are now correctly registered in the ai-red-teaming capability, resolving hard blocks on hosted-target runs like model-extraction and mesh playbooks.
  • AIRT agent guardrail for CLI provisioning. The ai-red-teaming capability now enforces a guardrail that prevents the agent from falling back to CLI environment provisioning, ensuring it always routes through the provision_environment tool.
  • Dev runtime sandboxes no longer fail after Workflows launch. The missing workflow module is now correctly bundled into E2B SDK templates, fixing sandbox start failures introduced by the Workflows feature.
  • Workflows catalog scoped to selected project. The Workflows catalog now filters by the selected project, and workflow graphs stay stable through polling, tab switches, and zoom changes without blinking or resetting.
  • SDK websockets floor raised. The SDK now requires websockets 15.0.1 or later, preventing runtime failures when fastmcp initializes in environments with websockets 14.x installed.
  • Org member suspension status accurate. Platform-suspended users now appear as “suspended” (not “active”) in org member tables, giving admins an accurate view of who can log in.
  • Org owner and member removal now requires confirmation. Removing an org owner or member in the admin panel now shows a confirmation dialog explaining what will happen before making any irreversible changes.
  • Form validation errors shown inline. Form validation errors now appear next to the relevant field instead of as generic toasts with no context.
  • Data grids show load failures with a Retry option. Data grids now show an error panel with a Retry option when a fetch fails, instead of displaying stale rows or a false empty state.