FAQ
Is Sirius free?
Section titled “Is Sirius free?”Yes. Sirius is free to download and use on any number of devices you own, for personal or commercial development. There are no plans and no tiers: you bring your own model keys and pay the provider directly, or run local models and pay nothing. The licence is the binding text.
Which models can I use?
Section titled “Which models can I use?”Anthropic Claude, Google Gemini, OpenAI, OpenRouter, Groq, DeepSeek, Mistral and xAI through their APIs; Ollama, LM Studio, llama.cpp and vLLM locally; and any other OpenAI-compatible endpoint. Pick a model from the picker in the chat, or with Sirius: Select AI Model from the Command Palette. See Providers and keys and Local models.
Does my code leave my machine?
Section titled “Does my code leave my machine?”Only in the request you send, and only to the provider you chose: the prompt, the context you attached or the editor included, and files a tool read. Sirius runs no relay. With a local model, nothing leaves the machine at all. There is no telemetry, no crash reporting and no account. See Privacy and where keys live.
Is this Visual Studio Code?
Section titled “Is this Visual Studio Code?”No. Sirius is a derivative work of Code - OSS, the MIT-licensed open-source foundation of VS Code; it is not VS Code and is neither produced nor endorsed by Microsoft. It does not use Microsoft’s branding, telemetry or Marketplace: extensions come from Open VSX, because Microsoft’s marketplace terms bar other products from using theirs.
Can I bring my extensions and settings?
Section titled “Can I bring my extensions and settings?”Yes. Sirius: Import from VS Code, Cursor, or Windsurf brings your settings, keybindings, snippets and extensions over from Visual Studio Code, Cursor, Windsurf (now Devin Desktop) or VSCodium, and reports what it imported. See Importing from another editor.
Where are my API keys stored?
Section titled “Where are my API keys stored?”In the editor’s secret storage, which is backed by your operating system’s keyring — never
in settings.json, never synchronised, never sent anywhere but the provider they belong
to. See Privacy and where keys live.
How does it update?
Section titled “How does it update?”The tarball and the Windows installer check the update server and update themselves
(Windows in place; on Linux the editor notifies you and opens the download page). The
.deb, .rpm and Arch packages update through your package manager; the pacman repository
is updated by the release itself. See Updates.
Why does Windows warn me on first run?
Section titled “Why does Windows warn me on first run?”The Windows installer is not code-signed yet, so SmartScreen shows its warning. Choose More info, then Run anyway. Every release asset is attested with GitHub build provenance and carries a sha256 sidecar you can verify. Signing is on the roadmap.
Is there a macOS build?
Section titled “Is there a macOS build?”Not yet. The packaging exists, but a macOS release needs an Apple Developer certificate for signing and notarisation; without it Gatekeeper refuses the app. Follow the GitHub issue to hear when it ships.
Is Sirius open source?
Section titled “Is Sirius open source?”No. Sirius ships under its own proprietary licence, and its source is
published on GitHub. Code - OSS and every third-party component keep their own licences,
reproduced in ThirdPartyNotices.txt.
Where do I report a bug or a security problem?
Section titled “Where do I report a bug or a security problem?”Bugs and feature requests go to GitHub issues. Security problems go through GitHub’s private vulnerability reporting, never a public issue — see the security policy.