Scylla
Sign InDownload

Support

Install Scylla

Windows requirements, installation, updates, and the first successful launch.

Scylla is a Windows desktop development workbench. The installer puts the Scylla application, its supporting runtime components, and the updater on your machine. Your AI provider accounts remain separate from Scylla and are connected after the application starts.

Before you install

Use a current, fully updated Windows machine and install Scylla under the Windows user account that will actually use the application.

Scylla runs approved provider tools, terminals, Git operations, and local project operations as the signed-in Windows user. Windows filesystem permissions still apply. Scylla does not replace Windows security or create a separate operating-system account for day-to-day work.

Scylla also uses embedded WebView2 surfaces for parts of the interface such as rendered content and browser-backed views. On current Windows systems the WebView2 runtime is normally already present. If a preview or browser-backed surface fails to initialize, verify that the Microsoft Edge WebView2 Runtime is installed and current.

Install

  1. Download the current Scylla installer from the Downloads page.
  2. Close any older Scylla instance before starting the installer.
  3. Run the installer and allow Windows to complete the installation.
  4. Launch Scylla from the Start menu or installed shortcut.
  5. If Windows displays a normal publisher or installation confirmation, review it before continuing.

Scylla is currently a pre-release product, so install the version distributed by the official Scylla Workbench site rather than copying application binaries between machines.

First launch

A successful first launch should open the Scylla workbench without requiring an AI API key just to reach the application.

From there, the normal setup sequence is:

  1. Open or add a project folder.
  2. Review Workspace Scope and choose the project folders Scylla may make available to Agents during the session.
  3. Choose a Primary project if more than one project is active. Primary is the fallback project when a chat or operation does not otherwise identify one.
  4. Connect a supported Agent Provider.
  5. Optionally add Knowledge Scope folders for non-project reference material.
  6. Review Policy, terminal, MCP, Connections, and Keyring settings before allowing consequential operations.

See First Launch for the full walkthrough.

Community, Professional, and Team

Scylla licensing and AI provider authentication are independent.

A Scylla license or Team entitlement determines your Scylla edition and usage rights. It does not provide OpenAI, Anthropic, GitHub, Cursor, or other provider access.

Likewise, signing into an Agent Provider does not sign you into your Scylla Account.

Team users normally activate the desktop through their Scylla Account after an organization seat has been assigned. See Desktop Team Activation.

Updates

Scylla checks for application updates periodically and can also expose an update action from the application.

When an update is available, Scylla verifies the downloaded update before handing it to the updater and installer. Allow the updater to close the running Scylla process, complete installation, and relaunch the application.

If an update fails:

  • close Scylla completely and retry;
  • confirm the installer is not being blocked by Windows or endpoint-management software;
  • verify that the download completed successfully;
  • use the current installer from the official Downloads page if the in-app update cannot complete.

Files Scylla creates

Scylla keeps application state under your Windows user profile and maintains project-specific configuration separately from your source code where appropriate.

Do not manually copy encrypted Keyring data between Windows users or machines and expect it to work as a portable credential store.

Project source remains in the folders you explicitly open or add to Workspace Scope.

If Scylla does not start

Work through these checks in order:

  1. Confirm Windows is fully updated.
  2. Restart Windows if an installer or runtime update is pending.
  3. Confirm the WebView2 Runtime is available.
  4. Launch Scylla normally rather than through an unusual compatibility mode.
  5. If the application previously worked, try the latest official installer over the existing installation.
  6. Collect the Scylla version, Windows version, and any visible error message before reporting the issue.

See Troubleshooting for provider, project, Keyring, Memory, and connection-specific issues.

Next

Continue with First Launch, then Configure Policy before allowing an Agent to perform write, shell, database, or external operations.