September 2026

← Back to Changelog

New Features:

• 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.

Improvements:

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

← OlderAugust 2026