Support & feedback

Something not working?

Vlocalhost runs on your machine, so we cannot see what went wrong unless you tell us. The app writes a short report you can read, check, and send.

Send us a diagnostic report

Takes about a minute. Nothing is sent until you send it.

  1. In the app, click “Report a problem” on the Record tab.

    It saves a report and opens the folder containing it. If the app will not open at all, run python vlocalhost.py --diagnose in the folder you installed to — it writes the same file.

  2. Read it. It is plain text.

    Your settings, package versions, the error, and the last lines of the log. No meeting audio, no transcripts, no notes, no file names. Home paths and your account name are replaced before it is written.

  3. Send it using one of the buttons below, attaching vlocalhost-report.txt.

    Drag the file straight into a GitHub issue, or attach it to an email.

Raise a bug

Public issue tracker. Best for reproducible problems — you can attach the report file directly and follow the fix.

Open a GitHub issue →

Email us privately

No GitHub account, or something you would rather not post publicly. Attach the report and tell us what you were doing.

Email support →

We never collect anything automatically. Vlocalhost has no telemetry and no crash-reporting endpoint. The report is a file on your disk; sending it is an action only you can take, and you can delete any line you are not comfortable sharing before you do.

Common problems

Worth trying before you write to us.

The installer says Python was not found

Install Python 3.9 or newer from python.org. On Windows, tick “Add python.exe to PATH” on the first screen of the installer — this is the single most common cause. Then run the installer again.

I used the ZIP and there is no desktop icon

Correct — the ZIP is deliberately portable. It writes nothing outside the folder you unpacked it into, which is why deleting that folder removes it completely, and why nothing appears on your desktop or in the Start menu.

The folder ships two helpers for exactly this. Double-click:

Create desktop shortcut.cmd

That puts Vlocalhost.AI on your desktop and in the Start menu, pointing at the copy you unpacked. It finds the real desktop folder even when OneDrive has redirected it. To take them away again:

Remove desktop shortcut.cmd

No registry writes, no admin rights, nothing outside your own home folder.

Chrome says “Failed — Virus scan failed”

This is not a detection. Chrome hands the finished download to Windows to be scanned, and that call failed — usually a third-party antivirus, a managed work laptop, or a Defender service that isn’t running. The file is never reported as malicious; the scan simply never returned an answer.

In order of least effort:

  1. Open Downloads (Ctrl+J) and press Retry. Transient scanner failures often clear on a second attempt.
  2. Take the ZIP instead, offered on the install page. Same build, no installer: unpack it and run Vlocalhost.cmd.
  3. Verify the file and keep it anyway — the SHA-256 for every release is published beside the download, so you can prove the bytes are the ones that were built.

If a scanner quarantines it outright, that is a false positive on an unsigned installer that unpacks a Python interpreter — a common shape for heuristics. Reporting it to your vendor helps everyone; so does telling us, because we submit these for reclassification.

Windows blocked the installer — “Windows protected your PC”

Expected, and worth explaining rather than waving away. The installer is not code-signed: a certificate costs a few hundred dollars a year, and even a signed one earns SmartScreen’s trust only after enough people have installed it. So Windows shows the warning. Click More info, then Run anyway.

You do not have to take that on faith. Every release publishes a SHA-256 next to the download; check the file you got matches before you run it:

Get-FileHash .\vlocalhost-1.1.1-windows-x64-setup.exe -Algorithm SHA256

Compare the result with …-setup.exe.sha256 on the releases page. If they match, the file is byte-for-byte the one that was built. If they do not, delete it and download again.

macOS says the file is from an unidentified developer

Do not double-click it. Right-click the file, choose Open, then confirm. macOS only offers that option on the right-click menu.

Notes are empty, or summaries never appear

Summarizing needs Ollama running locally. Check it is installed and the model is pulled:

ollama pull llama3.2

Recording and transcription work without it — you will still get a transcript, just no written summary. The diagnostic report tells you whether Ollama was reachable.

Nothing is transcribed, or the microphone is silent

List what the app can see:

python vlocalhost.py --devices

On macOS, allow the microphone permission prompt on first run. On Linux, install PortAudio (sudo apt install libportaudio2, or sudo dnf install portaudio). Silence is ignored on purpose — lines only appear when someone actually speaks.

The app opens and closes immediately

Run it from a terminal so the error is visible:

python vlocalhost.py --no-tray

Then send us the report from python vlocalhost.py --diagnose.

Where are my files?

Notes are saved in your notes folder, reachable from Open notes folder in the app. The log and diagnostic report sit in the app's config folder, which Report a problem opens for you.

Feature requests

Ideas are welcome in the same tracker — tag them however you like, we read everything. If it is about pricing or a team deployment, email is better.

Browse open issues →