Skip to content

For the complete documentation index, see llms.txt.

October 2026

New Features:

  • Collect Cursor sessions as native traces: Cursor joins Claude Code, Claude Desktop, and Codex as a native trace source for Promptless Instruction Governance. Analyzer releases 0.3.3 and later report Cursor support, and the default enrollment policy then includes Cursor. Rebuild your hub with trace collection enabled and refresh the Cursor pig plugin; an enrolled Cursor host uploads its desktop Agent sessions to your analyzer. Pilot on one host first. See Enroll your hosts.
  • See what shipped PIG fixes recovered: The Instruction Hub now has an Impact page that lists every fix whose pull request has merged, newest first. Each row shows the pull request, Instruction Hub, and merge time. Thirty days after the merge, each fix shows the agent time and tokens it recovered per analyzed session, compared with the 30 days before. The page for proposed fixes is now labeled Fixes and sits first in the Instruction Hub sidebar. See Measure what a fix recovered.

Improvements:

  • Get files from Promptless in Slack: Ask Promptless in a Slack thread for a file, such as a report it generated. Promptless uploads the file to that thread. File uploads need the files:write Slack permission. If your workspace lacks it, the Slack card on the Integrations page asks you to grant it. Until then, the rest of your Slack connection keeps working. See Ask for a file.
  • PIG 0.3.4 configures the collector Ingress in the bootstrap chart: PIG 0.3.4 is now the stable release for AWS. You set the trace collector’s hostname, ingress class, TLS Secret, and annotations in the pig-supervisor chart’s ingress values. Helm or your GitOps workflow owns the Ingress. Existing installations complete a one-time handoff that keeps the same Ingress and load balancer. Azure and Google Cloud remain experimental. See Upgrade an existing installation to 0.3.4.
  • Worker chart 0.3.5 uses pig Helm values: The manually managed worker chart reads its settings from the top-level pig key. The analyzer receives them as PIG_* environment variables. When you upgrade a manual installation from 0.3.4, rename instructionHub to pig in your values file. Secret references under secrets are unchanged. See Upgrade a manual installation. A supervisor-managed 0.3.4 installation needs a one-time supervisor bootstrap before it can update to 0.3.5 or later. See Upgrade a 0.3.4 installation to 0.3.5 or later.
  • PIG 0.3.6 is the stable release for AWS: PIG 0.3.6 uses database schema revision 5, which adds cloud agent enrollment. It supports PostgreSQL 15–18 on Kubernetes 1.30 or later. Install with Helm covers each step through a first verified session: release digests, collector Ingress values, and enabling analysis. Azure and Google Cloud remain experimental.
  • Redirects for changed page URLs: A suggestion that retires, moves, or renames a page now adds a permanent redirect from the old URL. The redirect leads to the page that now covers the topic and sits next to your collection’s existing redirects. The same suggestion points links elsewhere in the collection at the new page. For a feature that’s deprecated but still works, Promptless keeps the page and adds a deprecation notice that links to the replacement. See Redirects and Promptless.
  • Jira work runs as your service account: With an Atlassian service account attached, Promptless does all its Jira work as the service account. Without one, Promptless reads Jira as the person who connected Atlassian. It writes to Jira as that person only when your Knowledge Base or the current request explicitly permits the action. Replies also match how a task started. Mentioning or assigning Promptless gets an acknowledgement, progress updates, and an answer. A promptless label or a configured Jira trigger gets a comment only for a suggestion or an actionable blocker. See Reply on the ticket.
  • Chart your docs backlog week by week: The Impact page charts suggestions created, merged, and closed each week, and the backlog still open. See whether review keeps pace with drafting, and narrow the chart to the priorities you report on. See Measure the impact of Promptless.
  • Message the Promptless team from your editor: The Promptless MCP server can send a message to the Promptless team. Ask your editor to report a problem, a bug, or a feature request from the conversation you have open. See message_promptless_support.
  • Follow up on assigned suggestions from the weekly digest: The Slack digest lists assigned suggestions first, with their assignees, and links to just those suggestions. Every week, your team sees the assigned reviews that stalled after their first notification. See Weekly digest.
  • Attach files to task replies: You can now attach files or paste a screenshot when you reply in a task conversation. Send Promptless the spec or screenshot it’s missing while the task is still running, without starting a new task. See Attach files to a reply.
Newer →November 2026