Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>LivtNew to Visual Studio Code? Get it now.
Livt

Livt

Eccelerators

eccelerators.com
|
14 installs
| (0) | Free
Livt language support, project workflows, Test Explorer integration, CLI tools, and Copilot tools for VS Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Livt for Visual Studio Code

Livt for VS Code brings the core Livt edit, test, build, and package workflow into the editor.

Features

  • .lvt language registration, syntax highlighting, snippets, bracket rules, and word patterns.
  • Bundled Livt language server for hover, completion, diagnostics, document symbols, semantic tokens, inlay hints, formatting, code actions, and navigation.
  • Livt Project and Dependency views for source files, tests, generated outputs, package state, and common project actions.
  • Test Explorer integration with source-linked failures and rerun support.
  • VS Code tasks and command-palette actions for build, test, clean, sync, lock, validate, stats, vendor generation, and package publishing.
  • VS Code Language Model tools for Copilot Chat and Agent mode through #livt-* references.
  • First-run walkthrough for account setup, Livt and HxS installation, project build and test, vendor handoff, and Livt Agent.

Requirements

  • VS Code 1.100.2 or newer.
  • OpenJDK 17 or newer for the bundled language server.
  • The Livt CLI available on PATH, or configured through livt.path.

Install Livt using the official documentation: https://docs.eccelerators.com.

Getting Started

  1. Run Livt: Show Extension Diagnostics to verify Java, the Livt CLI, and the bundled language server.
  2. Open a folder with livt.toml, or run Livt: Initialize Project.
  3. Use Livt: Create Component or Livt: Create Test to add files.
  4. Run tests from the Testing view or Livt: Test Livt Project.
  5. Run Livt: Build Livt Project, then inspect generated output in the Livt Project view.

Language documentation starts at https://docs.eccelerators.com.

Configuration

Setting Purpose
livt.authentication.serverUrl Eccelerators OAuth server used for account sign-in. This is a machine-level setting.
livt.path Path to the Livt CLI executable.
livt.java.home / livt.java.path Java runtime used to start the language server.
livt.languageServer.enabled Enables or disables language-server startup.
livt.languageServer.trace Controls JSON-RPC tracing.
livt.languageServer.jvmArgs Additional JVM arguments for the language server.
livt.formatting.* Formatting enablement and formatter options.
livt.inlayHints.* Inlay hint enablement and detail controls.
livt.debugServer.* Connect to an externally running debug language server.

Account And Installation

Sign in to Eccelerators from VS Code to manage your account, install or update Livt, and synchronize licenses. After installation, the Livt language tools can be used without remaining signed in. Livt Agent access is authorized by the installed Livt license.

Livt Agent And Language Model Tools

Livt Agent provides Livt-aware questions, planning, project editing, build, test, dependency, and repair workflows in the secondary sidebar. Agent Context keeps project access explicit, and file changes remain reviewable and can be kept or discarded.

The extension also contributes Livt tools to compatible VS Code chat agents for project validation, build, test, clean, dependency management, package search, vendor generation, and publishing. Tool availability and approval behavior can be managed through the VS Code tools UI.

Troubleshooting

  • Run Livt: Show Extension Diagnostics and inspect the Livt output channels.
  • If Java is not found, set livt.java.home or livt.java.path.
  • If the CLI is not found, set livt.path.
  • If formatting is noisy while editing, set livt.formatting.enabled to false.
  • If language-server startup fails, run Livt: Restart Language Server after fixing configuration.

Known Limitations

  • Generated outputs are discovered from the configured outdir; stale artifacts are shown only when they can be determined from local files.
  • Vendor-specific generation depends on Livt CLI support and installed vendor tooling.

Release Notes

See CHANGELOG.md.

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