September 2026

← Back to Changelog

New Features:

• Propose Vale rules from your style guidance: During doc collection analysis, Promptless now proposes Vale rules derived from your style guidance, records them in your Agent Knowledge Base and, when it can place them in your repository, opens a suggestion to bring them in, supplementing any Vale setup you already have. You review the proposed rules and decide whether an advisory rule becomes enforced. See Propose Vale rules from your style guidance.

• Follow a Promptless task to its outcome from your editor: Over MCP, submit a documentation task—or ask Promptless to revise a suggestion it already made—and your editor follows the task in the same conversation and reports new messages, the result, and the docs PR link as they arrive. No more checking status by hand. It’s available to every organization. See MCP triggers.

• Enroll hosts that have no browser: You can now enroll a PIG host you reach over SSH, or any other host without a local browser. Run the host runtime’s enroll command with --device, then open the printed approval link on another device and approve the host there. See Enroll your hosts.

• Task outcome field and finished-task feed: Tasks now report an outcome of suggestions_created, no_change_needed, needs_input, or failed, so a Zap or other automation can act on how a task ended. outcome appears on GET /v1/triggers/{trigger_event_id}, MCP get_task_status, and the new GET /v1/triggers endpoint, which lists finished tasks newest first. The Zapier Documentation Task Finished trigger polls that endpoint. See API triggers.

• Start documentation work from a LaunchDarkly feature flag change (beta): You can now start Promptless documentation work when a LaunchDarkly feature flag changes, scoped by project, environment, or flag. It requires the LaunchDarkly integration connected and a configured LaunchDarkly flag trigger. See LaunchDarkly triggers.

Improvements:

• Provider-backed triggers require a connected integration: Adding, renaming, or modifying a GitHub, GitLab, Bitbucket, Slack, Microsoft Teams, ClickUp, LaunchDarkly, or Jira trigger now requires its integration to be connected. This applies in Form mode, YAML mode, and direct Agent Knowledge Base edits. Schedule triggers need no integration. See Connect a provider before you add its triggers.

• Resume a pending Slack admin-approval install: When your Slack workspace requires admin approval, your pending request now persists across page reloads and sessions. This works from both onboarding and the Integrations page. After an admin approves, select Continue in Slack to finish connecting. See Slack integration.

• Suggestions list as a review queue: The suggestions list shows each suggestion as a single row. Rows group by priority by default, or by doc collection or created date. Select a row to expand its description, changed files, and details, and edit its assignees, priority, and labels in place. The search field shows applied filters as removable pills and completes qualifiers from your organization’s labels, assignees, collections, and trigger sources. See Suggestions list.

• Promptless joins the public channels you configure for passive listening: When you configure a public Slack channel for passive listening, Promptless now joins that channel. It starts receiving messages without anyone inviting it first. Private channels and channels shared with another workspace through Slack Connect still need you to add Promptless in Slack. See Passive channel listening.

• Backfill status and suggestions visible to all members: Backfill status and the suggestions a backfill produced are now visible to all organization members, though viewing remains read-only. Previewing and launching a backfill remain admin-only. See Backfill suggestions.

• Rendered Markdown in suggestion comments: Suggestion comments in the dashboard—inline comments, citation threads, and overall discussions—now render GitHub-flavored Markdown as formatted content instead of raw text. Tables, task lists (shown as non-interactive checkboxes), and embedded HTML all render, so provider updates such as Vercel deployment summaries are finally legible. Wide tables and code blocks scroll horizontally within the comment card rather than overflowing it, and images render when their source passes the dashboard’s existing image-host policy—otherwise the comment shows the image’s alt text. There’s no new setting, API, or configuration to change: content that already uses these formats simply renders better.

• Comments stay visible after their referenced text changes: When a reviewer edits a commented line so the discussion’s referenced text is no longer current, that discussion—its comment and its citations—now stays pinned in its original file’s diff gutter instead of disappearing from there and being reachable only in the History & Collaboration tab. These pinned discussions still count toward the Show Comments and Show Citations toggles. The card is labeled with its original position—“Original line N” or “Original lines N–M”—and keeps its original excerpt and reply controls. Because the referenced text has changed, it no longer offers the “Show in diff” jump to a current line. Discussions whose original file is no longer in the diff at all are unaffected and still live only in the History & Collaboration tab.

• Receipt confirmation on Jira issues: Promptless posts an eyes emoji (👀) comment on the Jira issue as soon as it picks up a request, so the requester knows work is underway. The comment covers every Jira trigger path—the built-in label, mention, and assignment triggers plus your configured triggers. It’s automatic and needs no setup or configuration. It acknowledges receipt only and is separate from Promptless’s substantive reply, which still follows once the work is done.

• Mention a teammate in suggestion comments: You can now @-mention an organization teammate in inline and overall suggestion comments. The mentioned person gets an email that links straight to the comment. Mentioning by email someone who isn’t in the workspace invites them with collaborator access after a confirmation. A comment can mention up to 20 people, and mentioning the same person on the same suggestion again within 5 minutes of the first mention doesn’t send a duplicate email.

• Filter suggestions by GitLab MR source repository: The suggestions list’s trigger-source filter now has a GitLab MRs group alongside the existing GitHub group, so you can narrow the list to a specific GitLab merge request source repository. Mixed GitHub and GitLab selections persist in saved, shared, and bookmarked filter URLs.

• Find suggestions by source PR number: Search the suggestions list with source-pr:123 to find the suggestions a source pull request or merge request triggered. A bare #123 matches either a docs PR or a source PR with that number, and pr:123 matches only the docs PR. See Filter and search.

• Grant missing Slack permissions on your existing connection: Promptless now checks whether your connected Slack workspace has every bot permission the app currently requests. When any are missing, the Slack card shows a Grant additional Slack permissions callout that names each missing permission with a short description of the feature it enables, and includes an Update connection button. Selecting it re-runs Slack authorization to add them, and your connection, channels, and configuration stay intact.

• Discussions can’t be resolved while Promptless is working on them: In the dashboard, you can’t resolve a suggestion-review discussion while Promptless has queued or in-progress work on it. During that time, the Resolve control is disabled, and hovering over it tells you to wait until Promptless finishes before resolving. An indicator showing that Promptless is working still appears, so your review feedback stays visible while Promptless keeps processing it. You can still reopen a resolved discussion, and you can resolve one once its work finishes.

• Automated bot and system messages no longer clutter discussions: Imported messages from deployment bots and other system sources—such as the automated deployment summaries providers post—no longer appear in dashboard suggestion discussions. They’re left out of the discussion cards, history, previews, and reply counts, so a discussion shows human comments alongside Promptless’s own replies and citations. Human replies in a mixed thread stay visible even when a bot message in that same thread is hidden.

• Custom notification message format: A message format you define in notification_preferences.md now fully replaces Promptless’s default notification format—its default fields and its default set of links—instead of only adjusting tone on top of the default. A stated format is exhaustive: Promptless adds none of the default fields or links it doesn’t list. See Notification preferences file.

• One message format for notifications and escalations: Suggestion notifications and escalations now open with a short summary and end with labeled lines. A suggestion notification’s labeled lines link to the pull request, merge request, or ticket that started the work, the dashboard suggestion, the docs PR, and any Knowledge Base file Promptless recorded. When Promptless knows where a named ticket key such as INC-879 lives, it renders the key as a link. Every escalation opens with a bold banner, Blocked or Heads up, so you can tell a blocker that needs your input from a pointer at a glance. See Notification preferences file and Escalation channel.

• Citation discussions on generated docs PRs and MRs auto-resolve: On a generated documentation pull request or merge request, Promptless now marks each citation discussion resolved shortly after posting it—GitHub review threads through GitHub’s native thread resolution, GitLab discussions through GitLab’s native discussion resolution. The evidence stays attached to the diff, and a repository that requires every thread resolved before merging can still merge. A reviewer’s reply takes precedence: reply to a citation discussion, or reopen one Promptless resolved, and it stays as the reviewer left it. This applies to every organization, with no setting to configure.

• Citations now read as collapsible evidence: Citation comments in the dashboard now expand and collapse to reveal their referenced source, and they no longer offer a resolve action or a resolved state—because a citation is evidence, not something to resolve. Evidence links and any human replies remain.

• Suppress generated PR and MR description extras: Organizations can now set publishing.suppress_pr_description_extras: true to omit Promptless’s generated PR and MR body extras—the “Open in Promptless” link, the trigger events section, and the tip—so the body carries only the suggestion’s own description. This helps teams whose repository already has its own PR template. See Policies.

• Stale screenshots caught during any documentation edit: During any documentation edit, Promptless now inspects the screenshots already on the page it’s editing and replaces any that have fallen out of date with your product. It catches these stale screenshots whether or not the change that prompted the edit touched that page’s interface.

• Repo-committed screenshots appear in the Screenshot Updates gallery: The Screenshot Updates gallery now includes the screenshots a suggestion commits to a file in your docs repository, alongside the managed images Promptless uploads. The gallery and its sidebar badge count the same screenshots. A deleted screenshot appears as a Removed card showing the previous version, so you can review a screenshot’s removal from the gallery. See Screenshot Updates.

• Trigger events read the same across the dashboard: The Triggers page and a suggestion’s Triggers & Analysis tab now show each trigger as a row in a day-grouped list. A status pill on the row reports the outcome at a glance—researching, suggestion created, suggestion updated, no suggestion, or suggestion closed—and expanding a row reveals its stage timeline, research breakdown, and the agent’s response. See the Triggers page.

• Promptless stays quiet when a docs PR comment is addressed to someone else: In Listen to all comments mode, Promptless now recognizes when a comment’s question or request is addressed only to another participant and leaves it alone—no reply, no changes. A comment that doesn’t clearly address someone else still gets a reply, same as before.

• See when Promptless last received a GitLab webhook: GitLab merge request triggers now show when their last webhook arrived, color-coded by age, so you can spot a broken webhook setup. See GitLab merge requests.

• Correlate a submitted task with the suggestion it produced: Each suggestion in the GET /v1/suggestions feed now carries a trigger_event_id—the same id POST /v1/triggers returns when you submit a task—so an API or Zapier automation can match a task it submitted to the suggestion that resulted. See API triggers.

• SVG diffs render as images: SVG files in a suggestion now open as side-by-side Before and After images, so you can see how a diagram changed. To review the markup diff, select View source in the file header. See Image preview.

Bug Fixes:

• The Suggestions list opens with your saved filters: Opening the list from the sidebar restores your saved filters. This works even when they differ from the default view.

← OlderAugust 2026