IDE Partial Setup Guide
When the RunLogos source editor shows IDE Partial, TypeScript / JavaScript or some language services are usually already available, while one or more project language servers are missing, not visible to the GUI process, or detected but not started yet. This page explains how to install and troubleshoot language services for Python, Go, Rust, and Java.
What IDE Partial Means
RunLogos detects language services from the current project and shows an overall IDE status in the editor status bar:
| Status | Meaning |
|---|---|
IDE Ready | The language services required by the current project are running and can provide diagnostics, completion, navigation, and related features |
IDE Partial | Some language services are available, while others are missing, stopped, or need a fresh detection |
IDE Offline | No language service is currently available, or the status query failed |
Each language can also show a more specific status:
| Status | Meaning | Next step |
|---|---|---|
ready | The language service is running and can handle requests | Use it directly |
available | RunLogos detected the language server, but it is not currently running | Click Restart / Start |
unavailable | RunLogos did not detect the language server | Install the runtime or LSP, then click Redetect |
The built-in RunLogos panel keeps only short hints, current diagnostics, and quick actions; even when offline, it still tells users the next step. The website carries the full install guide, platform-specific commands, common PATH locations, and troubleshooting steps.
Python / Pyright
Python semantic features are provided by Pyright. RunLogos detects the pyright-langserver executable.
| Item | Details |
|---|---|
| Required runtime | Node.js / npm |
| LSP | pyright-langserver |
| RunLogos actions | Copy command, redetect, Restart / Start |
| Common macOS paths | /opt/homebrew/bin, /usr/local/bin |
| Common Windows paths | %APPDATA%\npm |
macOS:
npm install -g pyright
pyright-langserver --version
Windows:
npm install -g pyright
pyright-langserver --version
If the status still shows available after installation, click Restart / Start. If it still shows unavailable, check the global npm bin directory from npm config get prefix, add it to the system PATH, and restart RunLogos.
Go / gopls
Go semantic features are provided by gopls. Install the Go toolchain first.
| Item | Details |
|---|---|
| Required runtime | Go toolchain |
| LSP | gopls |
| RunLogos actions | Copy command, redetect, Restart / Start |
| Common macOS paths | ~/go/bin |
| Common Windows paths | %USERPROFILE%\go\bin |
macOS:
go version
go install golang.org/x/tools/gopls@latest
gopls version
Windows:
go version
go install golang.org/x/tools/gopls@latest
gopls version
If go is missing, install Go first and confirm go version works. If gopls is missing, run the install command, add ~/go/bin or %USERPROFILE%\go\bin to PATH, then click Redetect.
Rust / rust-analyzer
Rust semantic features are provided by rust-analyzer. Installing it through rustup is recommended.
| Item | Details |
|---|---|
| Required runtime | rustup / Rust toolchain |
| LSP | rust-analyzer |
| RunLogos actions | Copy command, redetect, Restart / Start |
| Common macOS paths | ~/.cargo/bin |
| Common Windows paths | %USERPROFILE%\.cargo\bin |
macOS:
rustup --version
rustup component add rust-analyzer
rust-analyzer --version
Windows:
rustup --version
rustup component add rust-analyzer
rust-analyzer --version
If rustup is missing, install the Rust toolchain first. If the component is unavailable, confirm the current toolchain is installed and usable, run rustup update, then retry.
Java / Eclipse JDT LS
Java semantic features are provided by Eclipse JDT LS. RunLogos does not automatically install JDT LS; it only provides the guide, copyable commands, and path hints.
| Item | Details |
|---|---|
| Required runtime | JDK |
| LSP | Eclipse JDT LS / jdtls |
| RunLogos actions | Copy command, redetect, Restart / Start |
| macOS recommendation | Install with Homebrew, or install JDK + JDT LS manually |
| Windows recommendation | Install JDK and JDT LS manually, then add the jdtls directory to PATH |
macOS:
java -version
jdtls --version
Windows:
java -version
jdtls --version
If jdtls --version is not available, install a JDK first, then install Eclipse JDT LS and add the jdtls directory to PATH. JDT LS uses workspace / cache directories for indexes and project state; those directories should not be committed to the repository.
How To Make RunLogos Detect The Installation
Use this order:
- Verify the command in a terminal, for example
gopls version,pyright-langserver --version,rust-analyzer --version, orjdtls --version. - Return to the RunLogos IDE Language Services panel and click
Redetect. - For languages with
availablestatus, clickRestart/Start. - If the language server is still not visible, fully quit and reopen RunLogos so the GUI process reads the updated PATH.
- On macOS, check
/opt/homebrew/bin,/usr/local/bin,~/go/bin, and~/.cargo/bin. - On Windows, check
%APPDATA%\npm,%USERPROFILE%\go\bin, and%USERPROFILE%\.cargo\bin.
Do not send License Keys, project source code, prompts, environment secrets, or private repository content to AI or commit them to a repository. Troubleshooting language services only needs command names, versions, PATH values, and the RunLogos status.
Common Errors
| Error | Meaning | How to fix |
|---|---|---|
package-manager-missing | npm, go, rustup, or another installer is missing | Install the required runtime first, then retry the LSP installation |
network-unavailable | The package manager cannot download dependencies | Check network access, proxy settings, or mirror configuration |
permission-denied | The global install directory is not writable | Use a user-level install directory, or fix directory permissions |
post-detect-failed | Redetect still fails after installation | Check whether PATH is visible to the GUI process, then reopen RunLogos |
lsp-start-failed | The executable exists but the language server failed to start | Run the version command in a terminal and confirm the runtime and dependencies are complete |
LSP exited with code 127 | The process could not find a binary or runtime dependency when starting | Check PATH, runtime installation, and differences between shell and GUI environments first |
If the command works in a terminal but RunLogos still cannot see it, the usual cause is a mismatch between terminal PATH and GUI PATH. Add the corresponding bin directory to the system-level PATH, fully quit RunLogos, and open it again.