Ask Promptless to update your configuration
Overview
Section titled “Overview”Ask Promptless to change your configuration, and it makes the change for you. You can ask in Slack, Microsoft Teams, or a task on the dashboard’s New Task page. Use it when describing a change is faster than editing promptless.yaml on the Configuration page yourself. For example, add a trigger for a new repository while you’re discussing it in a channel.
A configuration change is not a documentation suggestion. Asking Promptless to update your docs produces a suggestion that you review and merge. Asking it to update your configuration changes your settings directly, with no suggestion and no pull request.
Before you start
Section titled “Before you start”- To ask from chat, the Promptless app in Slack or Microsoft Teams. To connect it, see Connect Slack or Connect Microsoft Teams.
- For a provider-backed trigger, such as a GitHub PR trigger, the provider’s integration connected. Promptless can’t add, rename, or change that trigger until it is. See Connect a provider before you add its triggers.
Ask Promptless to change your configuration
Section titled “Ask Promptless to change your configuration”-
In Slack or Microsoft Teams, mention
@Promptlessthe same way you request documentation updates. -
Describe the configuration change in your own words. There is no fixed command syntax.
-
If Promptless asks a clarifying question, reply in the same thread.
Promptless validates the resulting configuration before it applies the change, so an invalid or unrecognized change isn’t saved. It then commits the change to promptless.yaml in your Agent Knowledge Base. Review the result on the Configuration page. To undo a change, revert it like any other commit, or ask Promptless to change it back.
To ask from the dashboard instead, enter your request on New Task and submit it. Leave out the @Promptless mention.
New Task accepts configuration requests even before your organization has any doc collections. For example, you can ask Promptless to add your first docs repository as a doc collection.
For how to work with Promptless in Slack and Teams, see Review from Slack and Teams.
Choose what to change
Section titled “Choose what to change”Promptless can change any setting promptless.yaml supports. These example requests work the same way in Slack, Microsoft Teams, and New Task. On New Task, leave out the @Promptless mention:
| Section | Example requests |
|---|---|
| Triggers | @Promptless add a GitHub PR trigger for the acme/api repo@Promptless stop watching the #random channel@Promptless watch all repos in the acme org for docs changes@Promptless only trigger on the docs/ directory in acme/api |
| Doc collections | @Promptless add the acme/docs repo as a doc collection@Promptless limit the acme/docs collection to the docs/ folder |
| Context sources | @Promptless remove the Notion context source |
| Policies | @Promptless send suggestion notifications to #docs-review@Promptless turn on auto-create PRs for the acme/docs collection |
For every field, see the Configuration reference.
Restrict who can change configuration from chat
Section titled “Restrict who can change configuration from chat”By default, anyone who can mention Promptless in a connected Slack or Microsoft Teams channel can ask it to change your configuration. In the dashboard, anyone who can create tasks on New Task can submit a configuration request. Editing on the Configuration page is limited to organization admins.
To limit chat changes to specific people:
-
Open
PROMPTLESS.mdin your Agent Knowledge Base. -
Add an allowlist of the usernames or handles allowed to change configuration through chat.
-
Select Save.
When an allowlist is present, Promptless makes configuration changes from chat only for the listed users.
See also
Section titled “See also”- Teach Promptless a custom task, to pair a trigger with written workflow instructions for a repeatable task
- Agent Knowledge Base, where
promptless.yamlandPROMPTLESS.mdlive - Configuration reference, for every
promptless.yamlfield