Get the Windows installer.
Use the Windows installer linked from this guide.
00 / Quick guide
Start safely.Stay in control.
Install the Windows studio, protect the source project, and choose deliberately whether an AI task runs locally or sends enabled context to a cloud provider.
01 / Install
A clean start on Windows.
Begin with a small test project. Confirm that writing, History, and export behave as expected before moving important work into the studio.
Complete setup.
Run the Windows installer and follow the normal setup flow.
Prove the loop.
Create a disposable project, write a scene, close it, and confirm it returns.
02 / AI privacy
Know where the context goes.
RaQuill is local-first, not offline-only. The active provider and enabled context determine whether selected material leaves your computer.
Supported local engines.
Local-provider workflows can keep supported inference on your machine.
Configured cloud engines.
Prompts, selected text, and enabled context may be sent to that provider.
Your decision.
Review the provider and context controls before sharing private material.
Connected content is not automatically sent to every model. A workflow may receive supported material from sources you enabled or selected for that task.
03 / Project safety
An export is not always a backup.
Manuscript files, project packages, History, snapshots, and recovery serve different purposes. Keep an independent copy of important work.
Protect the live project.
Your project and scene files are the durable source, not a derived index.
Use project export.
Create a project export or package when portability or backup is the goal.
Open the result.
After any important export, open the file and inspect what was produced.
04 / Support
Need a hand?
Include the RaQuill version and a short description of the problem. Never send API keys, credentials, or private manuscript text.