You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I am describing a concrete problem or use case, not just a vague idea.
Area
apps/web
Problem or use case
Users repeatedly invoke the same small set of skills and short prompts while directing agents. Today they must reopen the skill picker or retype the same text each time, even when those actions are used throughout a project.
Proposed solution
Add a project-specific row of customizable quick slot buttons above the composer. Users can add, remove, and reorder slots. Selecting a slot immediately submits its stored skill invocation or text through the same path as a manually entered message.
Why this matters
Quick slots reduce repetitive typing and picker friction while keeping frequently used, project-specific actions within one click.
Smallest useful scope
Support persistent quick slots in the web composer for the current project. Each slot needs a label and submitted value, plus add, remove, and reorder controls. Selecting a slot should immediately send its value through the active provider.
Alternatives considered
Issue #1547 proposes searchable saved prompt snippets that are inserted into the draft without sending. That helps with reusable text, but it does not provide persistent one-click actions for a project's most frequently used skills and prompts.
Risks or tradeoffs
Immediate submission makes accidental activation possible, so quick slots must be visually distinct from ordinary composer text and remain easy to remove or reorder. The row should also avoid taking excessive composer space.
This discussion was converted from issue #6612 on August 15, 2026 09:54.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/web
Problem or use case
Users repeatedly invoke the same small set of skills and short prompts while directing agents. Today they must reopen the skill picker or retype the same text each time, even when those actions are used throughout a project.
Proposed solution
Add a project-specific row of customizable quick slot buttons above the composer. Users can add, remove, and reorder slots. Selecting a slot immediately submits its stored skill invocation or text through the same path as a manually entered message.
Why this matters
Quick slots reduce repetitive typing and picker friction while keeping frequently used, project-specific actions within one click.
Smallest useful scope
Support persistent quick slots in the web composer for the current project. Each slot needs a label and submitted value, plus add, remove, and reorder controls. Selecting a slot should immediately send its value through the active provider.
Alternatives considered
Issue #1547 proposes searchable saved prompt snippets that are inserted into the draft without sending. That helps with reusable text, but it does not provide persistent one-click actions for a project's most frequently used skills and prompts.
Risks or tradeoffs
Immediate submission makes accidental activation possible, so quick slots must be visually distinct from ordinary composer text and remain easy to remove or reorder. The row should also avoid taking excessive composer space.
Examples or references
Contribution
All reactions