Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Cygnum DEV EditorNew to Visual Studio Code? Get it now.
Cygnum DEV Editor

Cygnum DEV Editor

CACI Enterprise Systems

| (0) | Free
Connect to Cygnum DEV. Only useful to CACI Cygnum developers.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Cygnum DEV Editor

Cygnum DEV Editor connects VS Code to a Cygnum DEV environment so you can authenticate, mount remote folders, browse source held on the server, and open UniBasic files directly in the editor.

Features

  • Sign in with the configured Microsoft identity provider.
  • Mount the Cygnum remote file system into the VS Code Explorer.
  • Open remote source files through the cygnum-dev-editor file system provider.
  • Automatically assign the unibasic language mode to supported Cygnum files.
  • Refresh mounted remote files without reconnecting.
  • Open a specific record directly by ID when directory-style browsing is not practical.

Commands

  • Cygnum: Login
  • Cygnum: Configure
  • Cygnum: Connect to Cygnum
  • Cygnum: Refresh Remote Files
  • Cygnum: Open Record By ID

Configuration

The extension contributes these settings:

  • cygnum-dev-editor.authentication.provider
  • cygnum-dev-editor.authentication.tenantId
  • cygnum-dev-editor.authentication.clientIdA
  • cygnum-dev-editor.authentication.clientIdB
  • cygnum-dev-editor.api.hostname
  • cygnum-dev-editor.api.port
  • cygnum-dev-editor.api.basePath
  • cygnum-dev-editor.api.filePath
  • cygnum-dev-editor.workspace.disableGitAutoRepositoryDetectionOnMount

Requirements

  • Access to a Cygnum DEV environment and its backing API.
  • A working Microsoft authentication flow for the configured tenant and client IDs.
  • VS Code 1.103.0 or newer.

Remote File System Notes

When a Cygnum workspace folder is mounted, VS Code and installed extensions may probe the mounted tree. This extension reduces unnecessary traffic by supporting refresh-on-demand, lazy folder opening, and optional disabling of Git auto repository detection for the workspace.

Known Limitations

  • The remote file system depends on backend endpoints being available and authorized.
  • Explorer behavior is still ultimately driven by VS Code's file system APIs, so some background probing can still occur.
  • Write support depends on the configured backend implementing the expected file system endpoints.

Release Notes

See the bundled changelog for version history.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft