Skip to content

For the complete documentation index, see llms.txt.

PromptlessPromptlessPromptless Documentation
Get a demoStart for free

August 2026

← Back to Changelog

New Features:

  • Re-review GitHub PRs as new commits land: A github_pr trigger now accepts a new opt-in trigger_on value, updated, that turns Promptless into a review bot for an open pull request: whenever new commits are pushed, it re-reviews the PR and keeps its suggestions current as the code evolves. It’s inert by default and requires an explicit repos list to enable (repos: all isn’t allowed), and it applies to GitHub only. See Trigger modes.

  • Start a Promptless session from a Jira ticket: A Jira ticket can now start a Promptless session—assign the ticket to Promptless, add a promptless label, @mention Promptless in a comment, or configure a trigger on a Jira project, label, or status—and Promptless replies on the ticket with the documentation PR linked. See Jira triggers.

  • Trigger documentation work from a GitLab merge-request comment: Mentioning @promptless anywhere in a merge-request comment now starts documentation work, bringing GitLab to parity with the existing GitHub comment-mention behavior. Matching is case-insensitive. Use @promptless-for-oss for OSS. GitLab also recognizes /promptless at the start of a comment line as a less-reliable alternative. A comment on a merge request Promptless opened revises that suggestion, while a comment on any other merge request starts a new documentation review for it. Because a mention is an explicit request, Promptless reviews that merge request even if the project isn’t in your trigger’s repo list—it only needs your GitLab connection to have access to the project. Unlike GitHub, a mention in a merge-request title or description does not trigger; only comments do. See GitLab merge requests.

  • Acknowledge GitLab merge-request comment mentions with a 👀 reaction: When you @mention @promptless in a GitLab merge-request comment, Promptless now adds a 👀 reaction to acknowledge it saw your request, bringing GitLab to parity with the existing GitHub behavior. The reaction appears even when Promptless decides no documentation change is needed. See GitLab merge requests.

  • Post citations as inline comments on GitLab merge requests: Citations for a suggestion now post as diff-positioned discussion threads directly on the GitLab merge request, bringing GitLab to parity with the existing GitHub behavior, with an unanchored file-and-line thread as a fallback when a citation can’t be anchored to the diff. See GitLab projects.

  • Run documentation checks on a schedule: Promptless now supports schedule triggers—run standing instructions on a repeating cron schedule, at most once an hour, in the timezone you pick (for example, a Monday-morning check that the changelog and release-notes page still agree). See Schedule triggers.

  • Triage every screenshot in one place: The new Screenshot Updates tab gathers every screenshot on an open suggestion into a single gallery grouped by doc collection, so you can spot and act on screenshots that are easy to miss one suggestion at a time. Click a screenshot to jump straight to its suggestion. See Screenshot Updates.

  • Start documentation tasks from your editor over MCP: Connect Promptless to an MCP client like Claude Code or Cursor and start documentation tasks, search existing suggestions, list your collections, and check task status without leaving your editor. The connection authorizes with OAuth, so there’s no API key to create or paste, and every org member can set it up for themselves. The existing API key path is unchanged for server-to-server callers. See MCP triggers.

  • Run the whole documentation loop from your editor over MCP: The editor connection now goes past starting tasks. Ask Promptless to revise a suggestion it already made and it updates the same docs PR instead of opening a new one, or set a suggestion’s labels and assignees, rename its title, and open its docs PR yourself, or close a suggestion you won’t ship. Check a task to get its outcome and docs PR link back, or recover one you lost the ID for by listing your recent tasks. You can now connect from Cursor, VS Code, or Codex CLI as well as Claude Code. See MCP triggers.

  • Serve workflow guidance to your editor as MCP skills: Promptless’s MCP endpoint now serves its own workflow guidance as loadable skills to editors that support the draft Skills extension (SEP-2640). The first is a backlog-triage workflow that walks through your suggestion queue and gives each one an outcome. To back it, search_suggestions gains a labels filter, so a reviewer can pull a labeled queue—say, every P0 suggestion—in one call. The extension is still a draft, so its shape can change. See MCP triggers.

  • Read suggestions and submit tasks over the /v1 HTTP API: The external HTTP API now lets any client submit documentation tasks, read a suggestion lifecycle feed, and list your doc collections, all authenticated with your organization’s sk-pl- API key. Task submission accepts an optional Idempotency-Key header so a retried request never creates a duplicate. See API triggers.

  • Hold multiple named API keys: Your organization can now hold multiple named API keys instead of just one. Name each key for its purpose, and create or revoke it without affecting any other key. This fixes the previous behavior, where generating a new key immediately revoked the old one and logged out every other caller. See API triggers.

Improvements:

  • CI failures now appear as a distinct “CI failed” event: When a check fails on a suggestion’s docs PR, it now shows up in the suggestion’s event timeline as its own GitHub-branded “CI failed” event, visually separate from other events. Previously this surfaced as a generic Promptless “Feedback” item, which made machine-reported CI status look like human feedback. The event’s summary names the specific checks that failed—for example, “build, lint failed.” When more than three checks fail, it abbreviates, as in “build, lint, e2e and 2 more failed.” The event is tied to the docs PR the failure came from.

  • Research breakdown now reads Knowledge Base inline and attributes delegated research: Each trigger’s research breakdown—on the Triggers page and a suggestion’s Triggers & Analysis tab—now shows Knowledge Base reads inline, in the sequence the agent read them, instead of grouped at the end. Delegated research appears as an attributed branch labeled with the subagent type and its tool-call count. A “research agents” callout appears next to the summary when Promptless delegates research. See Research breakdown.

  • search_suggestions now requires a search query: The MCP search_suggestions tool now requires a query of at least 3 characters and no longer returns all your suggestions when you call it without one. See MCP triggers.

  • Backfill first-approval GitHub PR triggers: A GitHub PR trigger that fires only on first approval can now be backfilled. The backfill preview lists open pull requests whose first approval landed within the selected window, including pull requests opened before the window. These triggers previously returned no backfill results. See Backfill suggestions.

  • Trigger cards now surface the agent’s response and inline research breakdown: Completed trigger cards now surface the agent’s recorded response for the run as an Agent Response: preview—most useful when a trigger finished without creating a suggestion, since it often captures why no change was made—and the trigger’s research breakdown is now reachable inline on the card through a collapsed Show details toggle, so you can open it in place without opening the trigger. See the Triggers page.

Bug Fixes:

  • Image changes now show a before/after diff and apply correctly: Image and screenshot changes in a suggestion previously appeared as empty file cards in the dashboard suggestion viewer; they now display as a side-by-side before/after image diff, and an added or deleted image shows only the side that exists. Suggestions that changed only images were also mislabeled as rejected and couldn’t be applied at all—they now show their real status and can be applied and published like any other suggestion. Finally, rejecting an individual image in a suggestion used to delete the file; it now restores the original version, matching how rejecting a text file already worked.
← OlderJuly 2026
↑↓ Select↵ Open