# October 2026

> For the complete documentation index, see [llms.txt](https://promptless.ai/llms.txt).

**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](https://promptless.ai/docs/governance/get-started/enroll-your-hosts#cursor-collection).
- **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](https://promptless.ai/docs/governance/findings-and-remediation/remediate-findings#measure-what-a-fix-recovered).

**Improvements:**

- **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](https://promptless.ai/docs/governance/deploy-the-worker/manage-updates-and-recovery#upgrade-an-existing-installation-to-034).
- **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](https://promptless.ai/docs/governance/deploy-the-worker/manual-helm#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](https://promptless.ai/docs/governance/deploy-the-worker/manage-updates-and-recovery#upgrade-a-034-installation-to-035-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](https://promptless.ai/docs/governance/deploy-the-worker/deploy-the-analyzer-worker) covers each step through a first verified session: release digests, collector Ingress values, and enabling analysis. Azure and Google Cloud remain experimental.
- **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](https://promptless.ai/docs/for-docs/connect/triggers/jira#reply-on-the-ticket).

← Older [September 2026](https://promptless.ai/changelog/changelogs/september-2026)