Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Language Server for Gradle by BitnoNew to Visual Studio Code? Get it now.
Language Server for Gradle by Bitno

Language Server for Gradle by Bitno

bitno

|
20 installs
| (0) | Free
A private, fast Gradle language server for VS Code
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Language Server for Gradle by Bitno

A private, fast and secure Gradle language server for VS Code.

Early development: this extension is still being built. Expect missing features, rough edges and breaking changes between versions.

Private, fast and secure by design

Built by a developer, for developers, from Serbia. Free, because developer tools should be.

  • Private: Your editor, your business: no telemetry, no account, and your code stays on your machine.
  • Fast: Starts only when you need it, and does just the work you ask for.
  • Secure: Installs nothing it hasn't verified, and never keeps a password in plain text.

Supported

  • Groovy DSL: build.gradle, settings.gradle, init.gradle and other *.gradle scripts
  • Kotlin DSL: build.gradle.kts, settings.gradle.kts and other *.gradle.kts scripts
  • Gradle: 9.0 or newer, the version the build's wrapper names

Features

  • Syntax errors as you type, from Groovy's and Kotlin's own parsers
  • Warnings for unknown blocks and properties in Groovy scripts, once the build has loaded
  • Kotlin's type errors and warnings in Kotlin scripts as you type, unknown names among them, once the build has loaded
  • Completion of the blocks, properties and methods a script can use where you type, for the build's own Gradle version
  • What the build's plugins add: extensions such as java {} and kotlin {}, configurations such as implementation(...), tasks and ext properties
  • Version catalogs: libs. accessors complete, also in plugins { alias(...) }, and hover shows an entry's coordinates and version
  • libs.versions.toml: tables, entries' keys, version.ref versions and bundles' libraries complete, and hover shows how scripts read an entry and what it loads
  • libs.versions.toml and gradle.properties: Ctrl+click or find references on a key lists the scripts' accessors and properties that read it
  • Ctrl+click on a property a script reads, as ${springVersion}, goes to where it's set: the script's own ext, gradle.properties, or a parent project's script, as subprojects { ext { … } } in the root's
  • Move to version catalog: a light bulb action turns implementation("g:a:1.2") into a libs.versions.toml entry and its libs. accessor, or uses the entry you already have
  • Rename a catalog entry from its key or from a libs. accessor, and its key, the catalog's references to it and every accessor in the build's scripts change together
  • A Gradle Tasks view in its own icon in the activity bar, with each project's tasks by group, their descriptions and a run button on each, the same tasks in Tasks: Run Task and tasks.json as "type": "bitno.gradle", and Gradle: Run Task… to find one by its path; each runs your build's wrapper in a terminal
  • The tasks you ran last first, under Recent in the Gradle Tasks view and in Gradle: Run Task…
  • A "Run" code lens above each task your script registers or configures, as tasks.register("greet"), once your build has loaded
  • Task names and paths in tasks.named("…"), dependsOn(":app:jar") and the like, from your build's projects once it has loaded
  • Module paths in the settings' include '…' and in project(':…'), from the folders below the build that have a build script, those not included yet among them
  • Plugin ids in plugins { id("…") }: Gradle's core plugins, those on the script's classpath, those your included builds declare, and the Gradle Plugin Portal's, segment by segment
  • Plugin versions in id("…") version "…", newest first, from the Gradle Plugin Portal
  • Dependency coordinates in implementation('…'), testImplementation("…") and every other configuration: group, module and version, newest first, from Gradle's module cache and Maven Central
  • Signature help while you type a call's arguments: each overload with its parameters' names, the one you're at highlighted, the Kotlin DSL's extension functions such as register<T>(name) among them
  • Hover with the member's signature, what a block configures and links that open Gradle's sources, else its Javadoc
  • What a dependency loads where the script doesn't write it out, in grey at the end of its line, as its artifact and the version it resolves to: 'org.projectlombok:lombok' shows lombok:1.18.42 in any configuration, "org.springframework:spring-core:${springVersion}" spring-core:6.2.1, its template filled in from the script's own strings, its ext and extra properties, gradle.properties or the parent projects' scripts, which hover and Move to version catalog read too, libs.mapstruct mapstruct:1.6.3 (or a plugin marker's id), alias(libs.plugins.spotless) com.diffplug.spotless:8.0.0, and a plugin applied without a version, as id("org.springframework.boot") in a subproject, org.springframework.boot:3.4.1, with the full coordinates on hover; where your build resolves another version than the one written, as conflict resolution or a BOM picks it, "com.fasterxml.jackson.core:jackson-databind:2.15.0" shows → 2.18.2
  • The same in libs.versions.toml: the version a version.ref names, the version your build resolves for a library that writes none, and → 2.18.2 where it resolves another; editor.inlayHints.enabled turns them off
  • Javadoc in hover and completion, from Gradle's sources and plugins' sources, its links opening the sources they name
  • Go to definition in Gradle's sources and in plugins' sources, both downloaded in the background the first time they're needed
  • Outline and folding of a script's blocks
  • gradle.properties and gradle-wrapper.properties: Gradle's keys and their values complete, and hover describes them
  • The server's status beside the language mode of Gradle's files: what it's doing or what failed, spinning while it loads a build or downloads sources, with a notification when that takes longer than 10 seconds; it comes into the status bar only when something failed, and opens the log
  • Syntax highlighting for Kotlin DSL scripts, which VS Code doesn't color on its own
  • Gradle's names colored by what they are, in both DSLs: blocks, properties, methods, configurations and tasks
  • When the server is nearly out of memory, it says so once and offers to double its memory and restart; set it yourself with bitno.gradle.server.maxHeap, as 4g

Requirements

  • VS Code 1.145 or later.
  • A Gradle build with a wrapper whose distribution has been downloaded, which happens the first time you run ./gradlew.
  • Network access on the first start. The server runs on Java 27, which the extension downloads into ~/.jdks (about 140 MB) when it isn't there yet, as Language Server for Java by Bitno does; your build can use any Java version Gradle supports.

Getting started

Open a folder with a Gradle build. Syntax errors and Gradle's API work at once; what the build's plugins add appears once Gradle has configured the build in the background, and again after you save a script.

What it contacts

  • Adoptium, over HTTPS: the server's Java runtime, on the first start without it.
  • Loading a build, Gradle downloads what ./gradlew would, from the repositories your build declares: your wrapper's distribution, your plugins and their sources, and your dependencies' POMs and BOMs. With Language Server for Java by Bitno, also the jars on your compile classpaths.
  • Gradle's sources, once per Gradle version, when your wrapper's distribution has none (-bin), from the server your distributionUrl names. They're kept only when they match Gradle's published SHA-256.
  • The Gradle Plugin Portal, while you type a plugin's id or version in plugins {}, never for a namespace your own plugins are in. Turn it off with bitno.gradle.plugins.portalSearch.
  • Maven Central, while you type a dependency in dependencies {} once your build has loaded, never for a group your own projects are in. Turn it off with bitno.gradle.dependencies.mavenCentralSearch.
  • Offline mode: turn on bitno.gradle.build.offline and Gradle runs with --offline, taking your dependencies and plugins only from its caches, for loads, compiles and the tasks you run alike.
  • Tasks run only when you run one, in a terminal with your build's wrapper, or when Language Server for Java compiles after you save.
  • Nothing else.

Loading a build runs its scripts as ./gradlew would, so open builds you trust.

Feedback

Found a bug, or missing something? Open an issue. Questions and ideas go there too, as a question. Blunt feedback is welcome.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft