Updated
Augment for VS Code
This guide uses LyraShield's integration registry for the ide surface. It shows the current setup strategy and client source; actual client loading and authenticated runtime acceptance are tracked separately below.
Connection setup
The registry's setup path for this client is Guided manual setup over local stdio.
Client activation instructions
Augment has no verified LyraShield marketplace listing. Run `npx -y lyrashield@0.2.14 login --oauth`, then add local stdio in Augment Settings → MCP → Import from JSON with command `npx` and args `["-y", "@lyrashield/mcp@0.2.12"]`. Install workflow skills with `npx -y lyrashield@0.2.14 skills install augment-vscode`; the installer preserves customized skills. Skills and custom commands require the Public Beta opt-in on VS Code extension 0.789.0 or later. Node.js 24 or later is required. Augment does not document generic OAuth or bearer-header setup for arbitrary remote servers, so use local stdio and the user-only credential store. Preserve existing server entries; verify skill discovery and make a read-only workspace call before treating setup as connected.
Augment has no verified LyraShield marketplace listing. Run `npx -y lyrashield@0.2.14 login --oauth`, then add local stdio in Augment Settings → MCP → Import from JSON with command `npx` and args `["-y", "@lyrashield/mcp@0.2.12"]`. Install workflow skills with `npx -y lyrashield@0.2.14 skills install augment-vscode`; the installer preserves customized skills. Skills and custom commands require the Public Beta opt-in on VS Code extension 0.789.0 or later. Node.js 24 or later is required. Augment does not document generic OAuth or bearer-header setup for arbitrary remote servers, so use local stdio and the user-only credential store. Preserve existing server entries; verify skill discovery and make a read-only workspace call before treating setup as connected.Important gotchas
- Skills, commands, MCP servers and rules are configured separately from Auggie CLI plugins. This entry has no persistent MCP config file because the IDE docs provide Settings Panel and JSON import rather than a stable on-disk path.
- Custom MCP remote HTTP/SSE configuration is documented, but generic OAuth or bearer-header authentication for arbitrary custom servers is not. Use local stdio with the LyraShield CLI credential store unless Augment documents that auth contract.
- VS Code Skills and custom commands are Public Beta opt-ins from extension 0.789.0. User guidelines have a separate VS Code extension version gate; see the official rules guide.
npx -y lyrashield@0.2.14 login --oauth to select a workspace for local stdio, or use a scoped workspace API key in an appropriate private environment. Never commit credentials.Native components and distribution
Documented client capabilities: skills, commands, rules. These describe what the client can load; use the installer and distribution details below to see which LyraShield components are available for this surface.
Install shared LyraShield skills
The pinned CLI includes a skills installer for this client. Preview its file changes first, then run the install command. Existing files that are not LyraShield-owned, or have been customized, are preserved.
npx -y lyrashield@0.2.14 skills install augment-vscode --project --dry-runnpx -y lyrashield@0.2.14 skills install augment-vscode --projectRestart or reload the client and verify its skill list. Local files do not prove discovery, authentication, marketplace listing or runtime acceptance.
Distribution route: Direct Augment IDE skills, commands, rules and MCP settings; registry state PREPARATION. Client distribution documentation.
Support evidence
Registry tier: COMPATIBLE. Evidence: DOCUMENTATION, checked 2026-10-01. Client version: not recorded; tested platforms: not recorded. No client runtime receipt is recorded.Marketplace state and runtime compatibility are separate claims.