Is your feature request related to a problem?
The "Load" button lacks clarity, making it unclear that it opens the configuration in an editable panel. Users discover the prompt editor only after clicking a config, leading to confusion about the flow of creating versus editing configurations.
Describe the solution you'd like
- Clarify the "Load" button: Rename or annotate it to better indicate that it opens the config for editing, such as "Load & Edit" or add a tooltip.
- Enhance prompt editor discoverability: Add a clear affordance—like an icon or inline hint—to indicate the prompt editor capability before the user interacts with a config.
Doc to refer: https://docs.google.com/document/d/1tcbaV0SHVzGDzMX43Y19iH6QMoZfCfAj19lh7Z9HAVQ/edit?tab=t.6u6pg5dlxx48
Original issue
Describe the current behavior
The "Load" button does not communicate that clicking it will open the configuration in an editable right panel — the affordance is unclear. The ability to open configs in the prompt editor is only discoverable after clicking on a config in the configuration library, with no prior indication. The "New Config" label implies creating something from scratch, but the actual flow often behaves like editing or versioning an existing setup. Additionally, users can rename configs inline within the flow, which makes it difficult to distinguish a renamed config from a genuinely new version, and the list/history view gives no clear signal about which state the config is in.
Describe the enhancement you'd like
-
Clarify the "Load" button: Rename or annotate the button to better convey that clicking it opens the configuration in an editable panel — for example, labeling it "Load & Edit" or showing a tooltip/subtitle that sets this expectation upfront.
-
Surface prompt editor discoverability: Do not rely on users stumbling upon the prompt editor integration by clicking a config. Add a visible affordance — such as an icon, label, or inline hint — that communicates this capability before the user interacts with a config.
Is your feature request related to a problem?
The "Load" button lacks clarity, making it unclear that it opens the configuration in an editable panel. Users discover the prompt editor only after clicking a config, leading to confusion about the flow of creating versus editing configurations.
Describe the solution you'd like
Doc to refer: https://docs.google.com/document/d/1tcbaV0SHVzGDzMX43Y19iH6QMoZfCfAj19lh7Z9HAVQ/edit?tab=t.6u6pg5dlxx48
Original issue
Describe the current behavior
The "Load" button does not communicate that clicking it will open the configuration in an editable right panel — the affordance is unclear. The ability to open configs in the prompt editor is only discoverable after clicking on a config in the configuration library, with no prior indication. The "New Config" label implies creating something from scratch, but the actual flow often behaves like editing or versioning an existing setup. Additionally, users can rename configs inline within the flow, which makes it difficult to distinguish a renamed config from a genuinely new version, and the list/history view gives no clear signal about which state the config is in.
Describe the enhancement you'd like
Clarify the "Load" button: Rename or annotate the button to better convey that clicking it opens the configuration in an editable panel — for example, labeling it "Load & Edit" or showing a tooltip/subtitle that sets this expectation upfront.
Surface prompt editor discoverability: Do not rely on users stumbling upon the prompt editor integration by clicking a config. Add a visible affordance — such as an icon, label, or inline hint — that communicates this capability before the user interacts with a config.