Affected area
Desktop app
Problem or workflow pressure
Agent Role prompts are useful as reusable instructions, but the current Role picker only applies the complete Role configuration. In an existing Session, users cannot send the Role's instruction as a standalone turn without manually copying it, and that workaround risks disturbing the current composer draft or attachments.
Desired outcome
From a persisted Session, make it possible to send a Role's instruction immediately as a normal Role-less user turn while preserving the Session identity, current composer text, mentions, pasted text, pending uploads, images, and files.
Proposed solution
Add a compact "Send instruction" action to the Role detail surface. On desktop, expose it in the detail header; on touch layouts, expose Apply Role and Send instruction from a long-press menu. Applying a Role should continue to use the existing configuration flow, while sending its instruction should use the Session's existing direct, guide, or queued submission route without selecting the Role.
Alternatives or workarounds
Users can copy the prompt from the Role detail and paste it into the composer, but that is slower and can overwrite or mix with an in-progress draft.
Trade-offs or non-goals
Limit the shortcut to already persisted Sessions so it never creates a Session or navigates to a different Session. Chat Landing and uncreated child tabs remain unchanged. Sending the instruction does not apply the Role's machine, agent, model, mode, or permission configuration. An unavailable Role can still expose its stored prompt for direct sending, while Apply Role remains disabled.
Additional context
The implementation belongs in the shared open-source components used by the desktop Session composer. It should reuse the existing Session submission path rather than introduce a new dispatch abstraction.
Before submitting
Affected area
Desktop app
Problem or workflow pressure
Agent Role prompts are useful as reusable instructions, but the current Role picker only applies the complete Role configuration. In an existing Session, users cannot send the Role's instruction as a standalone turn without manually copying it, and that workaround risks disturbing the current composer draft or attachments.
Desired outcome
From a persisted Session, make it possible to send a Role's instruction immediately as a normal Role-less user turn while preserving the Session identity, current composer text, mentions, pasted text, pending uploads, images, and files.
Proposed solution
Add a compact "Send instruction" action to the Role detail surface. On desktop, expose it in the detail header; on touch layouts, expose Apply Role and Send instruction from a long-press menu. Applying a Role should continue to use the existing configuration flow, while sending its instruction should use the Session's existing direct, guide, or queued submission route without selecting the Role.
Alternatives or workarounds
Users can copy the prompt from the Role detail and paste it into the composer, but that is slower and can overwrite or mix with an in-progress draft.
Trade-offs or non-goals
Limit the shortcut to already persisted Sessions so it never creates a Session or navigates to a different Session. Chat Landing and uncreated child tabs remain unchanged. Sending the instruction does not apply the Role's machine, agent, model, mode, or permission configuration. An unavailable Role can still expose its stored prompt for direct sending, while Apply Role remains disabled.
Additional context
The implementation belongs in the shared open-source components used by the desktop Session composer. It should reuse the existing Session submission path rather than introduce a new dispatch abstraction.
Before submitting