# Ansible deserves proper language server

**URL:** <https://forum.ansible.com/t/ansible-deserves-proper-language-server/46483>\
**Category:** Collection Development\
**Tags:** dev, ansible, ansible-lint, ansible-core\
**Created:** [October 15, 2026, 3:35pm UTC](https://forum.ansible.com/t/ansible-deserves-proper-language-server/46483 "2026-10-15T15:35:54Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![kks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kks/32/10352_2.png) [@kks](https://forum.ansible.com/u/kks)\
**Post date:** [November 8, 2026, 9:27pm UTC](https://forum.ansible.com/t/ansible-deserves-proper-language-server/46483/11 "2026-11-08T21:27:58Z")

</div>

zals only depends on `ansible-core` in the part that runs `ansible-playbook --syntax-check`. And the only reason to do that is to provide the same functionality that official ansible VSCode plugin provides. So if you do not need playbook syntax check, you do not need `ansible-core` at all.  
Same with `ansible-lint` - only used because official extension uses it.  
I am planning to create something similar to `ansible-static-lint` [Release Announcement: ansible-static-lint v0.7.0](https://forum.ansible.com/t/release-announcement-ansible-static-lint-v0-7-0/46356) hopefully more extendable, I want people and agents writing their own lint rules.  
Ansible-static-lint is also good project and deserve some attention.

---

_[View the full topic](https://forum.ansible.com/t/ansible-deserves-proper-language-server/46483)._