Repository navigation
Replies: 3 comments
|
This is something I'd use a lot. I'd like to save prompts I reuse and pick them from a list beside the message box, rather than keep retyping them. I found Cult UI's Prompt Library, which is close to what I have in mind. You can search saved prompts, browse by category, and add or delete your own. Picking one puts it into the input without sending, so you can make changes first. Would the T3 maintainers be open to this? I'd be happy to contribute an implementation once you approve the direction and initial scope. The link is just an example of the interaction, not a suggestion that T3 needs to use that component. |
|
I'd like this too, and I have a working branch to show one small shape for it. I won't open a PR unless a maintainer approves the direction and scope here. Proposed first scope (web and desktop, off by default)
Search, groups, a
Settings: Branch: main...pfaisant:t3code:feat/composer-actions (11 files, +437/−2 including tests and the composer user guide). Screenshots are from a dev server on Windows with isolated state. Two questions before I go further:
Written with Claude Opus 5.5 through Claude Code in T3 Code. |
|
@pfaisant +1 for opening this as a PR. The scope you've set out (a client setting, append-only, nothing auto-sent, off by default) is small enough to review and covers most of what I asked for in #6996. The part that matters most to me is that the label and the text stay separate, which your design already does. My labels are two or three words ("Commit + PR"), but the prompt behind each one is often 150 words or more of my usual workflow. The pill shows only the short label, and the full prompt is what goes into the draft. The spec in #6996 sets this out in more detail. On your two questions, from my side:
I'd like to see this on both desktop and mobile, so it would help if the stored shape (label and prompt) is easy to reuse in the mobile app later. An optional per-action "send immediately" flag, off by default, would also be useful in a later round. Once the full prompt is written, there's often nothing to edit before sending. Also related: #36376 proposes a row of follow-up pills that the model suggests after each reply. Saved actions and suggested follow-ups could share the same spot above the composer, so it might be worth a maintainer deciding on that placement once for both. |





Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/web
Problem or use case
Add support for user-defined saved snippets in the composer.
Proposed solution
Values:
Expected behavior:
Triggers:
"/s" command or dedicated button
Why this matters
This would speed up repetitive workflows and remove a lot of copy-pasting from external notes.
It’s especially useful for people who repeatedly run the same PR/review/CI prompts and want them to stay consistent.
Smallest useful scope
The smallest useful version is just:
Alternatives considered
Current workaround is keeping these prompts in notes, a text file, or another app and pasting them in manually.
Risks or tradeoffs
Main tradeoffs are added composer complexity and avoiding overlap/confusion with skills, slash commands, or automations.
Examples or references
Termius snipets:

Example snippets:
Contribution
All reactions