Skip to content

For the complete documentation index, see llms.txt.

PromptlessPromptless | Automatic updates for your customer-facing docs
Get a demoStart for free

July 2026

← Back to Changelog

New Features:

  • Live progress on Microsoft Teams mentions: When you @mention Promptless in a Microsoft Teams channel, the “I’m on it” acknowledgement now updates in place with short status phrases—like “Researching repo…” and “Preparing PR…”—as the agent works, right up until it posts the finished reply. This brings Teams to parity with the live status feedback already available in Slack.

  • Grant file access to private and shared Teams channels: The SharePoint site picker for Microsoft Teams now lists each private or shared channel as its own selectable site, so you can grant Promptless read access to the files attached in those channels—not just a team’s standard channels, which share the team’s root site. Microsoft only reveals a private or shared channel’s site to its members, so Promptless resolves these sites when you connect Teams and covers only the channels the connecting account belongs to. If a channel isn’t grantable yet, reconnect as a member of that channel to pull in its site. This affects only which attached files Promptless can read—the Promptless bot’s presence in your channels is unchanged. See Microsoft Teams administration.

  • Rename suggestions and keep them in sync with GitHub: You can now edit a suggestion’s title inline from its detail page in the dashboard. When the suggestion has an open or draft documentation PR, renaming it also updates the GitHub PR title. Promptless treats GitHub as the source of truth, so if you rename the PR on GitHub, that title flows back into the dashboard the next time you open the suggestion. Suggestions without an open PR are renamed locally. See Use the web interface.

  • Proactive alerts when an integration needs attention: Promptless now notifies you when a connected integration runs into trouble, so a broken connection doesn’t quietly stall your documentation. Notifications go to your organization’s configured escalation channel—Slack, Microsoft Teams, and/or email. A Needs reconnect state notifies you as soon as it’s detected, while a Problem state notifies only once it persists for more than 24 hours, so brief provider blips clear on their own. You get one notification per problem rather than daily repeats. Clearly names any impacted doc collections that can no longer be updated. See Integrations.

Improvements:

  • Rendered markdown in trigger detail cards: Opening a New Task, Deep Analysis, or Request Changes trigger to its full detail now renders the submitted text as formatted markdown—headings, lists, tables, code blocks, and inline images—instead of raw text. Embedded screenshots appear inline and scaled to fit, rather than spilling across the card as a wall of encoded characters, and a new copy button in the card header copies the raw markdown to your clipboard. Task triggers created through the API still display as plain text.

  • Full trigger text on the Triggers & Analysis tab and Triggers page: A trigger’s submitted text now displays in full on a suggestion’s Triggers & Analysis tab and on the standalone Triggers page, instead of being clamped to a few lines and cut off with an ellipsis. This makes it easy to read back a long submission in its entirety—such as a Deep Analysis instruction you want to reuse for a new request. The full text preserves your original line breaks and wraps at a comfortable reading width.

  • Richer Jira ticket context: When Promptless pulls a Jira ticket for context, it now reads much more of the issue—its type, priority, resolution, labels, components, affected and fix versions, parent and subtasks, and linked issues—alongside the summary, description, and comments. Promptless also reads organization-specific custom fields, such as a “Documentation” or “Public Description” field, giving the agent fuller business context when drafting documentation.

  • @promptless mentions from bots in PR reviews: Promptless previously dropped every bot-authored PR review, even one that mentioned @promptless—the earlier bot-mention change covered only bot comments. A direct @promptless mention in a bot’s formal PR review now takes priority over the bot filter and triggers documentation work, just like a mention in a comment, so a review bot—such as an automated code reviewer—can request docs. The mention can appear in the review summary or in an inline review comment. Bot reviews that don’t mention @promptless are still ignored.

Bug Fixes:

  • Admin-only agent behavior settings and doc-collection management: Changing agent behavior settings and creating, editing, or deleting doc collections now requires the Admin role, closing a gap where any organization member could change org-wide configuration. Doc collection management is admin-only in both the dashboard and the API—an API key can create, edit, or delete doc collections only when the user it was issued to is an admin. All members can still view the current agent behavior settings and the doc-collection list. On the Agent settings tab, non-admins now see “Agent behavior can only be changed by organization admins” in place of the editable controls. This matches the existing admin-only behavior for the Agent Knowledge Base and the Configuration page.

  • Create PR errored when a pull request already existed: Clicking Create PR on a suggestion whose branch already had an open pull request—for example, after a double-click or when a PR was opened outside Promptless—surfaced an error. Promptless now detects the existing pull request, records it on the suggestion, and opens it for you instead of failing.

  • Slack card status tag links to the pull request: Clicking the status tag on a Slack suggestion card—Pull Request, Published, or Rejected—now opens the linked GitHub pull request instead of the Promptless dashboard, matching the card’s existing View PR button. Suggestions without a pull request still link to the dashboard.

  • Slack link previews prompt a reconnect when a scope is missing: Sharing a Promptless suggestion link in Slack renders a preview card, which requires the links:write permission. Workspaces connected before this permission existed couldn’t render the card, so the link posted as plain text with no explanation. The Integrations page now flags an affected Slack connection as Needs reconnect—click Reconnect on the Slack card to grant the permission. Reconnecting keeps your existing connection, channel memberships, and configuration intact. See Updating Slack Permissions.

  • Slack card status tag links to the pull request: Clicking the status tag on a Slack suggestion card—Pull Request, Published, or Rejected—now opens the linked GitHub pull request instead of the Promptless dashboard, matching the card’s existing View PR button. Suggestions without a pull request still link to the dashboard.

← OlderJune 2026