Ask Promptless to update your configuration

You can ask Promptless in Slack or Microsoft Teams to change your configuration, and it makes the change directly. This is a conversational alternative to editing your configuration yourself in the Promptless dashboard. Describe the change you want in chat, and Promptless applies it.

What you can change

All Promptless configuration lives in a single promptless.yaml file in your Agent Knowledge Base, organized into four sections. Asking in chat can edit any of them:

• Triggers — add, modify, or remove a trigger, such as a github_pr trigger scoped to a repo, a slack_listen trigger for a channel, or a commit trigger.
• Doc collections — add, remove, or rescope a doc collection.
• Context sources — add or remove a context source.
• Policies — adjust publishing and notification rules, such as the notification channel or auto_create_pr.

These are common examples—you can change any setting that promptless.yaml supports, not just these. For the full field reference, see the Configuration reference.

How to ask

Mention @Promptless in Slack or Microsoft Teams the same way you already trigger doc updates, then phrase a natural-language request describing the configuration change you want.

For how to interact with the bot in Slack and Teams (message actions and mentions), see Review from Slack and Teams, and the Slack and Microsoft Teams integration pages.

Example requests

These are illustrative—you can describe the change in your own words rather than following a fixed command syntax. The same requests work in Slack and Microsoft Teams. The @Promptless phrasing here isn’t tool-specific.

You can manage your 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

You can add, remove, or rescope your doc collections:

• @Promptless add the acme/docs repo as a doc collection
• @Promptless limit the acme/docs collection to the docs/ folder

You can manage which context sources Promptless can query:

• @Promptless remove the Notion context source

You can adjust your publishing and notification policies:

• @Promptless send suggestion notifications to #docs-review
• @Promptless turn on auto-create PRs for the acme/docs collection

What happens: a direct config change, not a suggestion

Promptless applies the change directly and commits it to your promptless.yaml in the Agent Knowledge Base. No documentation suggestion and no pull request is created for a config change—this is distinct from the documentation-suggestion flow.

The two paths differ: asking Promptless to update your docs produces a suggestion you review and merge, while asking it to update your configuration changes your settings directly.

Promptless validates the resulting configuration before it applies the change, so an invalid or unrecognized change isn’t committed; if a request is unclear, Promptless may ask you to clarify before making the change.

Because each change is committed to your promptless.yaml in the Agent Knowledge Base, you can review the current configuration on the Configuration page, and the change can be reverted like any other commit.

Who can make changes

By default, anyone who can @mention Promptless in a connected Slack or Microsoft Teams channel can ask it to make configuration changes. This is different from editing configuration on the Configuration page, which is limited to admins.

To restrict who can make changes, add an allowlist of usernames or handles in PROMPTLESS.md in your Agent Knowledge Base, alongside promptless.yaml. When an allowlist is present, Promptless enforces it at runtime, so only the listed users can make configuration changes through chat.

To pair a trigger with written workflow instructions for a repeatable custom task, see Teach Promptless a custom task.