I am working in Yandex Cloud using my own organization, but SourceCraft has created a new one. How do I delete it?
To use a SourceCraft account, you need a personal organization, i.e., a workspace with you as the owner. During sign-up, SourceCraft looks for a suitable Yandex Cloud organization and, if it fails to find one, creates a new organization.
You cannot delete a personal organization directly. To delete it:
Contact support to select a different personal organization.
To switch to a new personal organization, you must be its owner.
I have created an organization in SourceCraft, but it turned out that I do not need it. How do I delete it?
Since each SourceCraft organization is tied to a Yandex Cloud organization, you can manage them in Cloud Center. If you have the required permissions, simply delete the Yandex Cloud organization; this will also delete the organization in SourceCraft.
SourceCraft Sites
How do I confirm ownership of a SourceCraft Sites website in Yandex Webmaster?
This will verify all repositories and sites in the organization. Learn more about configuring hosting here.
Technical questions about Code Assistant
General questions
How is the service currently called?
The service is now part of SourceCraft. Therefore, the full name of Yandex Code Assistant has been changed to SourceCraft Code Assistant. However, its current features are still the same.
Code Assistant is now also available in the built-in SourceCraft code editor.
The Code Assistant plugin is now available for Visual Studio Code, VSCodium, and JetBrains IDE versions 2026.2, 2026.1, 2025.3, 2025.2, 2025.1, 2024.3, 2024.2, and 2024.1.
Do I need a Yandex Cloud billing account to work with Code Assistant?
No. To work with Code Assistant, you will need continuous internet access.
How do I change a user authenticated in Code Assistant?
To authenticate in Code Assistant as another SourceCraft user, log out of your current account and re-authenticate as described in step 3 of Install and configure the plugin.
This is an error returned by the internal IDE library used for authentication in SourceCraft. To resolve this error, upgrade your Visual Studio Code version.
Below is an example of a Visual Studio Code build with the plugin support.
Reinstall the plugin but do not run authentication.
Set another browser as your default browser temporarily, e.g., Firefox.
In the new browser, go to the authentication page and sign in using your personal login@yandex.ru type Yandex account, ​​not your domain account.
In the management console, make sure you selected the correct account.
Go back to the IDE, click , type SourceCraft Code Assistant and select SourceCraft Code Assistant: Login.
After successful authentication, the SourceCraft Code Assistant Authenticated Successfully message will appear in the browser.
The plugin does not start in JetBrains IDE; 404 error; Code Assistant's suggestions not displayed
Try restarting the IDE.
Error during plugin installation: No plugins found. Check the log file for errors
This error occurs if the JetBrains IDE version is not supported by the Code Assistant plugin. Check the list of supported versions and make sure your IDE version is among them.
The JetBrains IDE plugin installs incorrectly
The plugin is installed in the IDE as a ZIP archive. Do not unpack the archive you downloaded.
Some browsers, such as Safari on macOS, automatically unpack the downloaded archives. To download the plugin file exactly as an archive, right-click the link with the plugin, select Download Linked File As..., and click Save.
Proxy authentication error in JetBrains IDE
Error message:
Failed to authenticate with proxy
Check if the proxy server is enabled in the IDE. If it is, disable it and try authenticating again.
If authenticated successfully, you will see this message:
Hi <username>! You've successfully authenticated, but SourceCraft does not provide shell access.
How do I use SSH over HTTPS port?
If your firewall blocks SSH connections and cloning over HTTPS with a personal token is unavailable, try cloning the repository via SSH over the HTTPS port. This connection is usually allowed by firewalls, but may be blocked by proxy servers.
To check if SSH connection is possible via the HTTPS port, run this command:
ssh -T -p 443 ssh.sourcecraft.dev
If authenticated successfully, you will see this message:
Hi <username>! You've successfully authenticated, but SourceCraft does not provide shell access.
Note
For port 443, use the ssh.sourcecraft.dev hostname, not sourcecraft.dev.
To clone the repository via port 443, run this command:
If connecting to ssh.sourcecraft.dev on port 443 works, you can configure SSH so that all connections to sourcecraft.dev automatically use this host and port.
To do this, edit the ~/.ssh/config file and add the following section to it:
Host sourcecraft.dev
Hostname ssh.sourcecraft.dev
Port 443
User git
To check that the settings are applied, connect to sourcecraft.dev again:
ssh -T sourcecraft.dev
If the connection is successful, you will see this message:
Hi <username>! You've successfully authenticated, but SourceCraft does not provide shell access.
How do I update my list of known hosts?
If this is your first time connecting to SourceCraft, you will get an unknown host warning:
The authenticity of host '[ssh.sourcecraft.dev]:443 ([<IP_address>]:443)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbp********.
This host key is known by the following other names/addresses:
~/.ssh/known_hosts:32: sourcecraft.dev
Are you sure you want to continue connecting (yes/no/[fingerprint])?