Skip to content

Workflow runs spawn ephemeral Bots from node config (not in sidebar) #1373

Closed

Description

@Birfy

Ask

Owner 2026-10-27: when starting a Workflow, spawn temporary Bots from each node’s Bot configuration to execute the run. These Bots must not appear in the left sidebar.

Behavior

  1. On run_workflow / UI start: for each graph node that names a Bot config (model, tools, role, etc.), create an ephemeral Bot instance for that run.
  2. Ephemeral Bots execute the node’s work for that run only (or until the run finishes / is cancelled).
  3. They must not be listed in the left sidebar (friends / Bot list). Permanent Bots stay as today.
  4. Cleanup when the run ends (or on failure/cancel): tear down ephemeral instances so they do not leak.

Out of scope

Done when

  • Starting a workflow creates ephemeral Bots from node configs; they run tasks; sidebar stays free of them; they are cleaned up after the run.
  • PR with Fixes #<this>; tests cover “not in sidebar” + cleanup.

Activity

  1. added
    enhancementNew feature or request
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    area:uiWeb/desktop UI and copy
    area:automationScheduled tasks and automation
    on Oct 27, 2026
  2. Birfy commented on Oct 27, 2026

    @Birfy
    CollaboratorAuthor

    Written-by: Chief

    Claiming. Workflow runs spawn ephemeral Bots from node config; they stay off the left sidebar and clean up after the run.

  3. added
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 27, 2026
  4. Birfy commented on Oct 27, 2026

    @Birfy
    CollaboratorAuthor

    Written-by: Chief

    Owner clarification 2026-10-27: the user must be able to configure these Bots’ system prompts and the flowchart either in Settings or via conversation (chat). Ephemeral run Bots still spawn from that config and stay off the sidebar.

  5. added a commit that references this issue on Oct 27, 2026
    bcb039e
  6. removed
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:automationScheduled tasks and automationarea:uiWeb/desktop UI and copyenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions