What Mull touches, what leaves your machine, and where your key is stored.
Mull runs on your computer. Your source code, local configuration, and command history stay on your machine. Nothing is uploaded to Mull or any Mull-operated service.
Mull authenticates with OpenRouter. The API key you provide is stored locally in ~/.mull/auth.json and is sent only to OpenRouter, the provider you choose. Mull never receives or forwards your key.
Set OPENROUTER_API_KEY in your environment to avoid writing the key to disk.
To answer a request, Mull sends the context you ask for — selected files, diffs, and conversation — to the OpenRouter endpoint you configure. The default is https://openrouter.ai/api/v1. Review what you include before sending.
Mull does not collect analytics, usage metrics, or crash reports by default. There is no account to create and no data shared back with the project.
The only external service Mull contacts is the model provider you configure (OpenRouter by default). Their handling of data is governed by their own privacy policy.
If these practices change, the updated policy will be posted here. This page describes the software as published on github.com/palmshed/mull.
Questions about data? Get in touch.