Run the docs loop from your editor, and more from September 2026
Many teams where engineers own the docs have written the same CI script. It diffs the pull request, asks a model to update the docs, and opens a PR. The script keeps no record of what it proposed last week, so it drafts the same change twice. When it misses a change, nothing tells you. A reader finds out first.
The biggest update this month closes that loop from inside the editor. Your coding agent can now hand documentation work to Promptless, follow it to a docs pull request, and ask for revisions, all in one conversation.
Run the documentation loop from your editor
Section titled “Run the documentation loop from your editor”Connect Claude Code, Cursor, VS Code, or Codex CLI to the Promptless MCP server at https://api.gopromptless.ai/mcp. In Claude Code, it’s one command:
claude mcp add --transport http promptless https://api.gopromptless.ai/mcpYou authorize once in the browser with OAuth. The consent page names the organization the connection acts in, so you know where your tasks go before you approve.
After that, you ask in plain language. A typical session goes like this:
- Your agent changes an SDK method. Ask it to check whether Promptless already has a suggestion for that change. It calls
search_suggestions, finds any live draft, and skips starting a duplicate. - If nothing live comes back, it submits a documentation task and follows it in the same conversation. It relays Promptless’s messages as they arrive, then the outcome and the docs pull request link.
- While the task runs, add to it: “Also cover the error responses.” If Promptless asks a clarifying question, you answer it in the editor.
- Once the suggestion exists, ask for a revision, and Promptless updates the same docs pull request. You can also set its labels, assignees, and title, open its pull request, or close a suggestion you won’t ship.
Your editor can auto-approve the five read-only tools. The six tools that queue or change work ask before they run, including when your editor follows the suggestion-triage workflow skill through a backlog. The MCP server is built in and available to every active member of your organization.
See MCP triggers for every tool and supported client.
Also shipped
Section titled “Also shipped”Start a Jira session when an issue reaches done
Section titled “Start a Jira session when an issue reaches done”Configure a Jira status-change trigger with is_done: true. A Promptless session then starts whenever an issue moves into a status in Jira’s done category, whatever your projects call it. Promptless reads the issue, then comments on the ticket and attaches the documentation pull request as a linked reference. The outcome shows up where the work was tracked. Jira triggers can also start a session when an issue is created or a label is added. See Jira triggers.
Scheduled documentation checks
Section titled “Scheduled documentation checks”A schedule trigger runs a standing instruction you write on a cron schedule, at most once an hour, in the timezone you choose. For example, every Monday at 9am, check your changelog against recent releases. Findings arrive as ordinary suggestions and follow your publishing and notification policies. When nothing needs to change, the run finishes quietly. Use it for the places where docs drift with no pull request to catch the change. See Schedule triggers.
GitLab merge requests
Section titled “GitLab merge requests”- Mention
@promptlessin a merge request comment to start documentation work. On a merge request Promptless opened, the comment revises that suggestion. On any other merge request, it starts a new review. That includes projects outside your trigger’s repo list, as long as your GitLab connection can access them. Promptless reacts with 👀 so you know it saw the request. - Citations post as discussion threads positioned on the diff of the documentation merge request. Promptless resolves each one after posting it. The evidence stays on the diff, and projects that require resolved discussions can still merge.
- When you set up a new merge request trigger, you can replay merge requests from the last 30 days. Use that first batch to calibrate Promptless and catch up on missed documentation.
See GitLab merge requests and Comment @promptless on a GitLab merge request.
Try it this week
Section titled “Try it this week”Connect the MCP server, then ask your editor to search your Promptless suggestions for the last feature you shipped. Start with Connect the server.