Ansible Language Server (zals) for VS CodeThis is what community says about this plugin.
Bradley A. Thornton aka @cidrblock on forum.ansible.com
Mark Bolwell (one of the contributors of Ansible-Lockdown) on forum.ansible.com Spend less time searching YAML. Spend more time writing Ansible. Find where a variable is defined and used, jump from a role call to its contract or implementation, and add debug tasks without breaking your flow. zals brings Ansible-aware navigation, documentation, completion, and refactoring into your editor, backed by a native language server. Install from Visual Studio Marketplace · Get it on Open VSX · Source code Why zals?
Get started
Try it now: right-click a variable and choose Find All References, hover over a role parameter, or use Go to Symbol in Workspace from the Command Palette. Using Remote SSH, WSL, or a dev container? Install zals on remote host.
or
The bundled server must match the host running the extension, not your local desktop. For offline or manual installation, download the matching platform's See it in actionAll eight recordings below show zals running in VS Code, from the Ansible community introduction. Follow a variable across your workspaceUse Find All References from a variable read or definition to see where that name appears. Use Go to Definition to inspect its bindings, and hover to see candidate values without leaving your file.
Find references to variable fields, tooFollow fields such as
References are static, workspace-wide name matches, not a simulation of Ansible execution. Variables with the same name can appear across roles; field references match the leaf field name, even on different objects. Add a debug task without typing the boilerplatePlace the cursor on a variable and open Refactor... to insert a debug task for it.
When you are done, use the code action inside the debug task to remove it.
Jump from a role call to its contractUse Go to Definition on a role name to open its argument specs, with role metadata or the main task file as fallbacks. See the role's interface without hunting through directories.
Go straight to the role's tasksUse Go to Implementations on a role name to open its main task file.
Understand role parameters where you use themHover over a passed parameter for its argument-spec documentation. Use Go to Definition to open the matching option, or Go to Implementations to find concrete values in the called role, such as defaults or vars.
Find tasks and roles by name, not by file pathRun Go to Symbol in Workspace to search playbooks, roles, and named tasks. Use the Outline view to navigate the current file.
Fits your Ansible projectzals recognizes common playbook and role paths, including tasks, handlers,
defaults, vars, and metadata. It also supports Ansible metadata files such as
Open Settings and search for
Focused, local, and open source
zals is an independent project, not an official Red Hat or Ansible extension. It focuses on editing Ansible YAML—not Lightspeed, MCP, execution-environment management, or the full ansible-dev-tools experience. It can serve as your Ansible YAML language extension without requiring the Red Hat extension. Feedback and supportSomething not working? Report an issue with your extension version, operating system or remote environment, and a small example. Feature ideas are welcome in the Ansible forum discussion. If zals makes your Ansible work easier, a review on the Marketplace or Open VSX helps others find it. License |







