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

# Changelog

Here's what's new in Codna, newest first. Codna is in active `0.1.0` development, so this page tracks each capability and fix as it lands — every entry maps to a real, merged change you can inspect on GitHub.

{% hint style="info" %}
Want the full commit-level history? Browse every merged pull request at [github.com/thyn-ai/codna](https://github.com/thyn-ai/codna/pulls?q=is%3Apr+is%3Amerged).
{% endhint %}

## July 2, 2026

**Local apply is safer under real test artifacts.** `codna fix --apply` now handles common untracked test/build cache files without failing after the agent has already produced a valid patch.

**Fixed**

* Local branch apply still fails closed on tracked/staged changes and on untracked files that conflict with patch targets.
* Unrelated untracked artifacts such as `__pycache__` no longer block the apply step.
* Generated cache artifacts created inside the isolated agent workspace are no longer captured as patch files.
* Packaged local workspaces use fast detached git worktrees when the checkout has no tracked changes, even if unrelated untracked cache files exist.

## June 21, 2026

**The documentation site is live.** Codna now has a complete, task-oriented documentation set — the pages you're reading — published straight from the repository and kept honest by an automated audit on every change.

**New**

* Full docs: Quickstart, How Codna works, CLI reference, Security autofix, MCP / IDE, GitHub Action, Configuration, and a help-center-style Troubleshooting.

**Fixed**

* The MCP server now surfaces a clean tool error — for example `codna_triage error: no API key — set CODNA_API_KEY` — when the key is missing or a repository path is invalid, instead of exiting the process.
* Reconciled every documented flag, command, and output with the actual CLI, including the GitHub Action reference, after an end-to-end accuracy pass.

## June 20, 2026

**Security-proof autofix.** Codna can now prove which scanner findings are actually reachable before it touches a line — then open fixes you can review and trust.

**New**

* `codna secure` ingests a CodeQL, Semgrep, Snyk, or Trivy SARIF report, classifies every finding (`exploitable` · `production-reachable` · `unreachable` · `unknown`), and opens one proven-safe pull request per reachable finding.
* `codna secure --fix --engine local` runs the full detect → fix → re-prove loop on your own machine through the Codna agent — self-hosted, no pull request required.

## June 15, 2026

**The `codna` command.** The first cut of the CLI that understands and fixes your repository.

**New**

* `codna triage` maps a repository and locates the code relevant to an issue — deterministic, for roughly zero model tokens.
* `codna fix` finds a bug's root cause, plans a patch, and (with `--apply` or `--open-pr`) runs a risk simulation before writing anything.
* `codna fix --open-pr` and the **GitHub Action** turn a failing CI run into a reviewable fix pull request.
* `codna mcp` runs Codna as an MCP server, so Cursor and Claude Desktop can use it directly.

**Security**

* Resolved the initial CodeQL code-scanning alerts and hardened path handling in the security proof runner.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.codna.ai/reference/changelog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.