Skip to content

CL-6979: Do not auto-host Myra on blank new workbenches - #373

Closed
TheGreatAxios wants to merge 4 commits into
mainfrom
cl-6979-new-channels-do-not-auto-host-myra
Closed

TheGreatAxios wants to merge 4 commits into
mainfrom
cl-6979-new-channels-do-not-auto-host-myra

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

Summary

Blank / Just start talking workbench creates no longer auto-invite Myra or send her definitionId. Named templates still mint against the setup agent so greeting and connect cards have a sender.

Outcome

  • no auto-invite Myra on create
  • unmentioned does not wake Myra if absent
  • routing mention/reply/explicit host
  • routines don't require Myra on the open room
  • no silent purge

Note

Worktree at commit time only contained instant-agent-create product+test changes. If ensureMyraWorkbench remains in routine land-hop elsewhere, CL-6980 deletes that helper and rebase will retarget to generic Myra DM open.

Test plan

  • Unit: blank create asserts no definitionId on POST body and zero invite calls

Blank / "Just start talking" creates mint a kind:workbench room with no
definitionId and no invite. Named templates still launch against the
setup agent so greeting and connect cards have a sender.
@TheGreatAxios

Copy link
Copy Markdown
Contributor Author

Superseded by the stacked coworker IA PR (this rewrite from origin/main). Closing rather than merging: the five drafts contradict each other on create/sidebar/Myra-home.

@TheGreatAxios
TheGreatAxios deleted the cl-6979-new-channels-do-not-auto-host-myra branch August 25, 2026 15:40
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.

1 participant