Skip to main content
Skip documentation navigation
Developer docs

Get started

SoterAI Lite

Local extension protection, privacy, license and recovery limits for Windows developers.

Hands-on estimate · 4 min

What this guide does not cover

  • Documents the Windows x64 0.7.0 release candidate, not final acceptance on other operating systems or remote environments.
  • Protection covers supported managed AI routes, not unmanaged file reads, uploads, or bypasses by code running as the same user. Review recovery and retained-data limits before uninstalling.

Protection scope

SoterAI Lite helps Windows developers reduce accidental secret sharing through supported managed AI routes. Protection depends on the configured tool and route. Unmanaged file reads and uploads remain outside this protection, and code running as the same user can bypass cooperative controls. This is not an OS sandbox, a universal file-access firewall or a guarantee that secrets cannot leave the machine.

This guide covers the packages/soterai-lite source for the 0.7.0 Windows x64 pre-release candidate, not every Marketplace version. Its exact-package final acceptance and publication remain unverified. Linux, macOS, remote and virtual workspaces have not been accepted for this candidate. Check the version and its own documentation before installing.

View published Marketplace versions

Install and check the local candidate

The package keeps the extension identity soterai.soterai-ide-guard and existing soterai.* settings. Its manifest requires VS Code ^1.85.0; the packaging script targets win32-x64. The build includes the extension, local AI broker and MCP server. Local setup requires no SoterAI account, administrator access, VM or external controller; optional AI providers can have their own account requirements.

  1. Obtain a trusted VSIX for the version and Windows target you intend to evaluate. In the editor's Extensions menu, choose Install from VSIX. The Marketplace link above does not establish that this exact candidate is published.
  2. Open one local filesystem project. Review workspace trust before enabling integrations or file changes; restricted mode still permits local analysis.
  3. Run SoterAI: Open Control Panel, then SoterAI: Run Safe Demo Scan. Use the built-in example rather than real credentials for an initial check.
  4. Run SoterAI: Show AI Route Coverage. Review a tool's proposed configuration changes before opting in. A setting, badge or synthetic demo is not proof that a real tool used the managed route.

Local defaults and optional network routes

These are the declared machine-scoped defaults, shown for review in User Settings rather than as a project policy to distribute. Local live scanning is enabled by default and can inspect supported content without asking before each local scan. Managed safe-file releases, configuration changes and vault migration have separate review requirements.

User settings — selected defaultsJSON
{
  "soterai.cloud.enabled": false,
  "soterai.privacyMode": "local",
  "soterai.scan.remoteEscalation": "never",
  "soterai.telemetry.redactedEvents": "off",
  "soterai.audit.storeRawPrompts": false,
  "soterai.dependencyGuard.osvMode": "ask"
}
  • Provider traffic: the OpenAI-compatible and Anthropic-compatible provider URL settings start blank. Configuring a provider and routing a tool through the broker can send inspected public code and text, including values the filters do not recognize. Turning the separate cloud preference off does not disable provider traffic.
  • Dependency advisories: owner-invoked checks can ask to send package names, ecosystems and versions to OSV. The default is ask; never keeps those checks on local heuristics. The MCP dependency check is an offline advisory, not a complete vulnerability audit.
  • Telemetry: redacted events are off by default. The inspected telemetry sender has no remote send implementation; an opt-in may show minimized metadata in the editor's telemetry output. Editor, operating-system and other vendors' telemetry are separate.
  • Managed scope: a trusted window can start its own loopback broker. Use its current displayed URL, not an assumed fixed port. Other tools, direct file reads and independent uploads remain outside the broker. Approved readers can share returned text, and an application given vaulted values can transmit them.

Privacy and license documents

These are versioned reference copies for 0.7.0. SoterAI Lite uses the Business Source License 1.1. Its additional use grant allows non-production use and internal production use within a single entity. Commercial hosted or managed AI-security services for third parties and competing products require a separate commercial license. Read the complete terms rather than treating the Marketplace's Free label as unrestricted use. The license specifies a Change Date of 2030-06-25 and Apache License 2.0 as the Change License, subject to its version-specific timing terms.

The current packaging script includes LICENSE.md and PRIVACY.md, and generates THIRD-PARTY-NOTICES.md from the components bundled in each build. The notices linked here are an archived 0.7.0 reference. Check the exact VSIX for its build-specific notices; these website links are not proof of the contents of an installed package.

Recovery and removal

Removing the extension does not automatically restore protected files or erase retained policy and encrypted backup data. Before uninstalling, stop managed tool sessions and review the undo commands for changes you enabled, such as Restore Broker Integration and the tool-specific configuration restores. Changed files or ownership can prevent a restore; retain the receipt and resolve the conflict rather than forcing an overwrite.

Complete Safe Vault Recovery handles interrupted migration. Restoring original values through Restore File From Encrypted Backup is a separate explicit disclosure: it makes sensitive values readable in the project again. Saved restrictions do not prevent other same-user software from reading those originals. Encryption keys use VS Code SecretStorage; ciphertext without the required keys is not a usable recovery plan.

The versioned privacy statement describes a Restore changes before removal archive flow, but this source snapshot does not register that general command. Do not assume automatic archival or post-uninstall recovery in your build. Verify the installed version's actual recovery receipt and preserve required encrypted backups and key access before deleting extension storage or an editor profile. No recovery flow can recall prior uploads or guarantee protection from code running as the same user.

Report an issue

Optional analytics

Google Analytics, when configured, and Cloudflare Web Analytics load only if you allow them. Sign-in cookies and product audit records are separate. Privacy policy

Optional analytics is off.