Something is not working
Installation problems, errors, unexpected behaviour, performance questions about your own hardware.
support@onequill.devOneVir support
Help starts with a clear description.
Tell us where you got stuck and what you expected to happen. The more precisely you describe it, the faster we can answer.
Support routes
How does OneVir work?
Questions about capabilities, configuration choices, providers, policy or licensing for a specific use.
help@onequill.dev01 What to include
Six details that save a day.
Remove API keys, passwords, tokens and personal content from anything you send. OneVir's decision audit already records decisions without prompts, responses or tool arguments.
- Version and platform. Your OneVir version, operating system and, for engine issues, the GPU and driver.
- The steps. What you did, in order, until the problem appeared.
- Expected and actual. What you expected to happen and what happened instead.
- The message. The exact error text or a short log excerpt around it.
- The route. Whether the request ran locally or through a provider, and the model or alias it used.
- Configuration. The relevant part of your configuration, with every secret removed.
02 Look first
Answers already inside OneVir.
Many questions are answered by records OneVir keeps for you.
Activity and recent decisions
See where each request ran, which rule or alias chose the route, and whether it was served from cache.
Performance
CPU, memory, GPU, disk and network, with OneVir's own share shown separately, sampled every second.
Built-in API reference
Every OneVir instance serves its own typed API reference and OpenAPI document for the exact version you run.
Before installing or upgrading
Back up first. Then upgrade.
Follow the installation instructions and requirements published with your release. Keep a backup of your configuration and stored state before an upgrade that changes either.