Skip to content

Parent automation runs to their creating threads - #3061

Closed
bb-slop-cop[bot] wants to merge 1 commit into
mainfrom
slopcop/issue-3060
Closed

bb-slop-cop[bot] wants to merge 1 commit into
mainfrom
slopcop/issue-3060

Conversation

@bb-slop-cop

@bb-slop-cop bb-slop-cop Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Human comments

What was wrong

The automations agent-run dispatcher preserved the automation's creator thread in storage but omitted that relationship from threads.spawn, so the server created every new run thread without a parent. The direct reproduction and root-cause report is https://get-bb.github.io/reports/issues/3060.html.

What changed

  • Conditionally forward the stored creator thread as parentThreadId when an automation spawns a new agent-run thread.
  • Preserve parentless spawning for automations created outside thread context.
  • Add plugin-harness regression coverage for both cases.
  • No wire, schema, migration, dependency, or generated-file changes.

How you verified

  • Before the production change, the focused regression test failed because the recorded spawn payload had no parentThreadId.
  • After the change, the focused regression test passed.
  • pnpm exec turbo run test --filter=bb-plugin-automations --force — 82 tests passed.
  • pnpm exec turbo run typecheck --filter=bb-plugin-automations — passed.
  • git diff --check — passed.
  • Changed-line count against origin/main: 47 additions, 0 deletions across 2 files.
  • The exact push range and working tree were clean in the EAP codename scan.

Fixes #3060

AGENT GENERATED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automation runs are spawned as siblings of the thread that created them

1 participant