# Autocomplete and Documentation issues in the Julia plugin for VSCode

**URL:** https://discourse.julialang.org/t/autocomplete-and-documentation-issues-in-the-julia-plugin-for-vscode/133367
**Category:** VS Code
**Tags:** documentation, autocomplete
**Created:** [October 22, 2025, 6:47pm UTC](https://discourse.julialang.org/t/autocomplete-and-documentation-issues-in-the-julia-plugin-for-vscode/133367 "2025-10-22T18:47:31Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![joemaik](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@joemaik](https://discourse.julialang.org/u/joemaik)
#### Post date: [October 22, 2025, 6:47pm UTC](https://discourse.julialang.org/t/autocomplete-and-documentation-issues-in-the-julia-plugin-for-vscode/133367/1 "2025-10-22T18:47:31Z")

</div>

I am running VSCode 1.105.1 with the julialang.language-julia plugin version 1.149.2.

TL-DR: I am having issues getting Autocomplete and the Documentation running for basic Julia packages such as LinearAlgebra, inside VSCode with the Julia plugin.

I am just experimenting with a very basic Julia script, containing

using LinearAlgebra  
A = [1 2; -1 1]

When I type “de”, say, I wait for the AutoComplete, which doesn’t show “det”, which is the determinant function in the LinearAlgebra package.

Another issue is that when I search for “det” in the documentation, it also cannot find its documentation.

I have read another post on the topic, where the suggestion was to add an include statement. I am wondering whether there are other workarounds. Thank you!

Edit: after looking at some error messages, it looks like the issue I am facing has to do with SymbolServer. I will get back to this when I get the chance.

Edit 2: using juliaup, I installed 1.11.7, which is older than what I was using (1.12.1), and autocomplete and the documentation magically worked for the LinearAlgebra package. The errors went away. I think the issue was with julia 1.12.1 being more strict about how and when packages should be loaded/imported, but perhaps the Julia plugin 1.149.2 needs some small modifications in order to take these Julia changes into account. I could be wrong, but this is my analysis. In any case, it is solved!