> For the complete documentation index, see [llms.txt](https://www.quillaudits.com/quillshield/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.quillaudits.com/quillshield/changelog/readme.md).

# Changelog

New updates and improvements to QuillAudits.

{% updates format="full" %}
{% update date="2026-11-12" tags="feature,workflows" %}

## Workflows and Workflow Studio

Every audit now follows a **workflow**. Keep the **QuillShield Audit Agent** (still the default), pick an official workflow that goes deep on one kind of bug, add one from the **Marketplace**, or build your own in **Workflow Studio**: describe what to look for in plain words, and the workflow assistant designs the stages and writes every agent's instructions in 1–3 minutes. Refine it by chatting, undo any change, save versions, and run it from the audit wizard's new **Workflow** step at the same price.

[Read the Workflows update](https://www.quillaudits.com/quillshield/changelog/2026/workflow-studio.md)
{% endupdate %}

{% update date="2026-09-30" tags="pricing,feature" %}

## Lower scope-curve prices, signup credit, and GitLab.com

Full audits now use **QS-PAYG-USD-V6**: `charm(max(49, 3 × L^0.7))`. The floor is still **$49**. Examples: 100 BLOC → **$79**; 1,000 BLOC → **$379**; 10,000 BLOC → **$1,899**; 40,000 BLOC → **$4,999**. Above 40,000 BLOC remains a custom quote.

New accounts receive **$50** signup credit once (email, Google, GitHub, or GitLab). It is bonus credit, covers at most half of a post-coupon order, and expires in 6 months.

You can sign in with **Continue with Google**, **GitHub**, or **GitLab**. GitLab.com projects support merge-request and commit scans. Completed audits can be published to the QuillAudits leaderboard and a public report.

Read the September 30 update
{% endupdate %}

{% update date="2026-09-15" tags="feature,ci" %}

## Ask AI, share links, and CI/CD App automation

Documented the full product surface: **Ask AI**, read-only **share links**, GitHub **App** PR/commit automation, team email invites, optional docs at checkout, per-user wallets, and in-app Support.

CI/CD light scans now document **ancestor** baselines, fail-on severity, and “recommend full audit” (not a hard block) for large diffs.

Read the September 2026 update
{% endupdate %}

{% update date="2026-08-26" tags="pricing,ci,feature" %}

## Scope-curve pricing and CI/CD Checks

Full audits moved to scope-curve pricing (then **QS-PAYG-USD-V4**, coefficient **5**). Current quotes use **QS-PAYG-USD-V6** (coefficient **3**) — see the September 30 update. Floor **$49**, custom quote above **40,000 BLOC**. The old $599 entry tier and marginal brackets are retired.

**CI/CD Checks** scan GitHub pull requests after a completed full-audit baseline. Completing a full audit grants **5 free** light scans; after that, light scans are **$5 + $0.10** per extra ΔSLOC above 50.

Also in this release: MCP (`@quillaudits/mcp`) for Cursor and Claude, Telegram notifications, PDF reports, and Refer & Earn.

Read the full August 2026 update
{% endupdate %}

{% update date="2026-05-08" tags="feature" %}

## Pay-as-you-go wallet and Refer & Earn

Checkout is quote → order → pay. Prepaid dollars, refund credits, and promotional credit apply before Stripe. Refer & Earn: friends get **$20 off** their first paid audit; you earn credit when their audits settle.

Read the wallet and Refer & Earn notes
{% endupdate %}
{% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.quillaudits.com/quillshield/changelog/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
