2.9.26
Released 2 Nov 2026
LibrePatch is an AI agent for Windows 10/11 that explores a project, runs your build and test commands and shows every file change as a diff. Version 2.9.26 needs no account to run.
.12 itemsLICENSE.txtread okSPDX3 matchesCONTRIBUTING.mdread oklicence-notes.txtsavedReleased 2 Nov 2026
Setup program download
Single .exe file
Interface languages
x64 architecture
Shows Update button
Open source coding means working on software whose source code is published under a licence that lets anyone read, use, change and share it under stated conditions. Read the licence first. LibrePatch helps with the practical side: it explores a repository, opens the licence and contributing files, runs the project's tests and shows each change as a diff in version 2.9.26.
Open the project's folder in a new chat and pick Ask first. The agent uses list_dir to show the top-level structure, read_file to open the LICENSE file and grep to search the source files for SPDX lines. Free and open source software normally keeps its licence in a LICENSE or COPYING file in the root folder. The 3 files to read first are LICENSE, README and CONTRIBUTING. Nothing changes yet. Every result appears as a card in the chat, and you read the licence text yourself before you decide whether the project's rules allow the change you have in mind.
list_dir . → top-level folders
read_file LICENSE.txt → licence text
grep SPDX → 3 matchesA typo fix is a small change that is easy to review. The agent uses grep to find the misspelled word, read_file to open the page and edit_file to correct it, and the change appears as a diff that you accept or reject. Shell then runs the project's own test command and reports the real exit code. Before contributing to open source, prepare by reading the CONTRIBUTING file and a few recent diffs to learn the project's style. Keep it small. You write the pull request and send it yourself, and the diff for a single typo is 1 changed line.
grep teh → 1 match
read_file docs/install.md → read ok
edit_file docs/install.md → +1 -1
Shell your test command → exit 0Shell runs the project's own build command and its test command, 2 commands in total, in the environment you chose: Windows, WSL or SSH to your own server. The agent reports the real exit code of each command, and an expanded card shows the full output. A passing exit code is a good sign, not a proof. Read the output. When a test fails, the agent uses grep and read_file to find the failing code, proposes a fix with edit_file and shows the diff. You review it and run the tests again.
Shell your build command → exit 0
Shell your test command → exit 1
grep FAIL → 2 matches
edit_file src/parser.txt → +2 -2Finding a maintainer for an open source project starts with the CONTRIBUTING file, which usually says where to ask and what a good description contains. Once your change passes the tests, the agent uses read_file to read the changed files and that file, then write_file to save a draft description as a new text file. The draft says what changed and why in 3 short paragraphs. Read it. You edit the wording, follow the project's policy on AI-assisted changes and send the pull request yourself.
read_file CONTRIBUTING.md → read ok
read_file docs/install.md → read ok
write_file pr-description.txt → savedLibrePatch 2.9.26 runs the tools itself and shows the real result of each action, while a typical chat assistant describes the steps for you to run. You review every diff.
| Typical chat assistant | LibrePatch | |
|---|---|---|
| Actions | Describes what to do | Runs the tools itself |
| Output | Gives a summary | Shows the full output |
| Files | You copy the changes | Edits files and shows a diff |
| Control | You apply changes yourself | Ask first and Plan only modes |
Beginners who are new to open source programming are the first group. They use LibrePatch to read the README, CONTRIBUTING and LICENSE files of a project and to see what each one asks of a contributor. Start small. Permissive licences such as MIT, BSD and Apache 2.0 allow reuse with few conditions, mainly keeping the notice.
Developers who fix code in unfamiliar projects use grep to find where a bug lives and read_file to open that file. A full stack project often mixes several languages, so an open source contribution there begins with a search across the whole folder. You test the fix yourself. The agent shows each command result as a card.
Careful contributors and small teams build a licence inventory of their dependencies. The agent reads the dependency and licence files and writes a CSV table with 4 columns: package, version, licence and note, which you check against the licence texts. It is not legal advice.
Open source coding is writing or changing software whose source code is published under a licence that lets anyone read, use, change and share it under stated conditions. Visible code is not enough. Code with no licence is, in most countries, not free to reuse, so check the licence file or ask the author before you copy anything.
Yes, libreprogramming.org is the official LibrePatch website, and its download button gives the setup program of about 34 MB for Windows 10/11. The installer is not code-signed yet, so compare its SHA-256 checksum with the published manifest before you choose Run anyway in the SmartScreen warning. Compare the two values.
No, LibrePatch needs no account to run on Windows 10/11. A cloud AI provider that you connect may require its own account and may charge separately, while a local model or the built-in model is ready to use without your own endpoint. Accounts depend on the model. Pick the model that suits your task and test it first.
LibrePatch is an agent for Windows that explores the repository, reads the LICENSE and CONTRIBUTING files, edits files with a diff for you to accept and runs the project's own build and test commands. Shell is not limited to the working folder. You decide. You review the diff and send the contribution yourself.
No. LibrePatch gives no legal advice. The agent can open the LICENSE or COPYING file, list the SPDX lines in the source files and summarise what the text says, but you read the licence text yourself and ask the project or a lawyer when it is unclear.
Yes, in part. web_search finds public project pages and http_get reads a documentation page, and list_dir then shows the structure of a project you have chosen. You decide which project suits you and read its rules. Pick 1 project first.
The Send feedback button inside the app is the way to report a bug or ask a question. Name the version. Describe what you did and what you expected, and say which version you run, for example 2.9.26 if you use the current build.
The 34 MB setup program installs LibrePatch on Windows 10/11, and the app shows an Update button when a new version is ready. Begin with a typo or a licence inventory. Pick 1 small task.
Download LibrePatch for Windows ↗Every page of this website is available in 20 languages. The app interface itself has 13 languages.
Product features ↗ Model configuration ↗ Workflow examples ↗ Download LibrePatch ↗ Questions about contributing to open source ↗ Privacy policy ↗