LiveQuill
Edit your local website by asking.
A floating prompt bar for any local site: type a change, the model of your choice edits your real files, and the page reloads.
Website · Install · Models · FAQ
A real, unedited first run with Claude Code (Haiku). MP4 version.
Why LiveQuill
- Ask on the page. Describe the change on the page you are looking at. The model finds the code, edits it, and the page reloads.
- Any model. Cloud APIs, local models, or the coding agent you already use, even if you only have the Claude Desktop or ChatGPT app.
- A new site in a minute. A short wizard starts from a template or a blank page. No technical skills needed.
- Nothing to lose. Every request is a version you can preview and go back to, with one-click Undo. Zero dependencies, nothing added to your project.
Install
Linux and macOS, with Python 3.10 or newer.
curl -fsSL https://ybucaille.github.io/livequill/install.sh | sh
No root, no git, no pip: the script checks and installs a single file, then creates the livequill command. If Python is missing, it tells you how to install it on your system.
Other ways to install, and uninstall
| pipx / uv | pipx install livequill or uv tool install livequill |
| Single file | Download livequill.pyz from a release and run python3 livequill.pyz |
| From source | git clone https://github.com/Ybucaille/livequill.git && ./livequill/bin/livequill |
| Uninstall | curl -fsSL https://ybucaille.github.io/livequill/install.sh | sh -s -- --uninstall (or pipx uninstall livequill) |
Update
Run the install command again: it replaces LiveQuill with the latest release and keeps your settings and sites.
curl -fsSL https://ybucaille.github.io/livequill/install.sh | sh
With pipx or uv, run pipx upgrade livequill or uv tool upgrade livequill. From source, run git pull. Check your version with livequill --version, and restart LiveQuill after updating.
Get started
livequill
- Choose a model. The first launch opens the setup page. Click a model detected on your computer, or paste an API key.
- Create a site. On My sites, click New site, pick a template, give it a name. Or add a site you already have.
- Ask. The site opens with the floating bar. Try “make the hero title red”, watch it change, then click Undo.
Command-line options
| Option | Description |
|---|---|
FOLDER |
Add this folder to your sites (if needed) and open it. Without it, the dashboard opens. |
--proxy URL |
Serve FOLDER behind your dev server (Vite, Next, Astro…) instead of serving its files. |
--port N |
Dashboard port on 127.0.0.1 (default 8777). Each site gets its own port after it. |
--config FILE |
Alternative config file (default ~/.config/livequill/config.json). |
--no-open |
Do not open the browser. |
Screenshots
 My sites. All your projects, with a live thumbnail. |
 New site. Pick a starting point and a name. |
 Setup. Detected models are one click away. |
 The bar. Live answer, files changed, Undo. |
Models
| Providers | What you need | |
|---|---|---|
| On your computer | Ollama, LM Studio, llama.cpp, any OpenAI-compatible server | The app or server running. Free and private. |
| In the cloud | Anthropic, OpenAI, Google Gemini, Mistral, OpenRouter | An API key, pasted on the setup page or read from your environment. |
| Coding agents | Claude Code, Codex, Gemini CLI | The CLI, or just the Claude Desktop or ChatGPT app, signed in to your account. |
Switch models at any time from the bar. Reasoning and Fast appear when the model supports them.
Details per provider
| Provider | Notes |
|---|---|
| Anthropic | Key from console.anthropic.com. Effort levels on Claude 4.6+, Fast on Opus 5.5 / 5 / 4.8. |
| OpenAI | Key from platform.openai.com. reasoning_effort on o-series and gpt-5. |
| Google Gemini | Key from aistudio.google.com. Thinking budget (2.5) or level (3). |
| Mistral | Key from console.mistral.ai. |
| OpenRouter | Key from openrouter.ai/keys. Capabilities are read for each model. |
| Ollama | ollama serve, then ollama pull qwen2.5:7b-instruct (any model that supports tools). |
| LM Studio | Developer tab → Start server. |
| llama.cpp | llama-server -m model.gguf --jinja. |
| Other | Any OpenAI-compatible server (vLLM, LocalAI, Jan, Groq, DeepSeek…): base URL, optional key, model name. |
| Claude Code | claude signed in, or the Claude Desktop app. Runs confined to the project, see SECURITY.md. |
| Codex | codex login, or the ChatGPT or Codex app. Runs in its sandbox, but can read your whole disk: see SECURITY.md. |
| Gemini CLI | gemini installed. Experimental: not tested yet. |
Privacy and safety
- Local only. LiveQuill listens on
127.0.0.1and checks a session token on every call. - Your keys stay on your computer. They never reach the browser, and are masked in logs.
- The model stays in your project. No path outside it, no
.gitor.envfiles, no shell commands. - Every change is backed up before it happens, so Undo always works, CLI agents included.
How each protection works is described in SECURITY.md, where you can also report a vulnerability privately.
FAQ
Does my code leave my computer?
Only with a cloud provider. With Ollama, LM Studio or llama.cpp, everything stays on your computer. With a cloud API, your request, the page context and the files the model reads are sent to that provider, like with any coding assistant.
Can I use it without an API key?
Yes. Install Ollama, run
ollama pull qwen2.5:7b-instruct (a 7B model or larger that supports tools works best), and pick it on the setup page. If you have Claude Code, Codex, or just the Claude Desktop or ChatGPT app, LiveQuill uses it with your existing sign-in.
What if the model breaks something?
Click Undo in the bar, as many times as you need. To go further back, open History (the clock button), choose the Versions tab, preview any earlier version, and click Go back to this version.
Does it work with React, Vue, Svelte or Next.js?
Yes. Keep your dev server running and add the site with its address, under Advanced (or run
livequill --proxy http://localhost:5173 ./my-app). LiveQuill adds the bar to its pages and keeps hot reload working.
Where is my data stored?
Your models, keys and sites are in
~/.config/livequill/config.json. New sites go to ~/LiveQuill/sites by default. Each site gets a .livequill/ folder with its backups and history. Uninstalling LiveQuill removes none of them: delete them yourself if you no longer need them.
Can I use it in another language?
The interface is in English for now, with a language menu ready for more. Adding a language is one translation file: see CONTRIBUTING.md. The model itself answers in the language you write in.
Roadmap
- Dynamic sites with a disposable demo database, so the model can work on data-driven pages safely.
- More templates and languages in the new-site wizard and the language menu.
- Point and ask: click an element on the page to scope the request to it.
- Review before writing: see the proposed changes and accept or reject them.
Contributing
Contributions are welcome: providers, themes, templates, translations and fixes. Start with CONTRIBUTING.md, which also explains how LiveQuill works inside.
License
MIT © 2026 Ybucaille
1 maintainer
Metadata
1 maintainer
Release files for livequill 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| livequill-0.3.1.tar.gz | 120.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| livequill-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 231.7 kB
Release files / livequill-0.3.1.tar.gz
| Download URL | livequill-0.3.1.tar.gz |
|---|---|
| Size | 120.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec448f8f57b4cca9f61c2d819a5f5aa4ea7cfe38aa67f59fda4d1e4a5200a4c7
|
|
BLAKE2b-256 checksum How to use checksums |
d99d88f4faa68c9cf3f48ca7ea31903281344995986963be8f095395faacf8a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / livequill-0.3.1-py3-none-any.whl
| Download URL | livequill-0.3.1-py3-none-any.whl |
|---|---|
| Size | 111.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1db1781831ba91061e252c9670ef0615e2e8bf7f97a957090e411b33927b58cf
|
|
BLAKE2b-256 checksum How to use checksums |
1aa89e9abceedcbc3620a2738bd9d698433f8a53c6d6c1fa58421c625b5c1c5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for livequill 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for livequill-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
