> For the complete documentation index, see [llms.txt](https://boxlang-ide.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boxlang-ide.ortusbooks.com/language-tools/overview.md).

# Overview

BoxLang language tools are built around the BoxLang Language Server. It gives editors a shared set of smart features through the Language Server Protocol.

This keeps diagnostics, hints, and formatting consistent across supported IDEs.

### Core components

#### BoxLang LSP

The [BoxLang Language Server](https://github.com/ortus-boxlang/boxlang-lsp) is the main implementation. It parses BoxLang code, tracks project context, and returns language features to any compatible editor.

It powers:

* diagnostics for static analysis
* hints for symbols, definitions, and type information
* formatting and project-aware configuration support

#### LSP4J

[LSP4J](https://github.com/eclipse-lsp4j/lsp4j) provides the Java bindings for the Language Server Protocol. It handles the protocol message model between the editor and the BoxLang server.

That lets BoxLang focus on language behavior instead of protocol plumbing.

### Diagnostics

Diagnostics report problems directly in the editor. They help catch issues before runtime.

Current checks include:

* unused variables
* unscoped variables
* duplicate members

You can control rules, severity, and file scope in `.bxlint.json`. See [Linting](/language-tools/linting.md).

### Hints

Hints surface useful language information while you type. They reduce context switching and speed up navigation.

These tools include:

* code outlines
* function and definition lookup
* type hints and inline language information

### Formatting

Formatting keeps BoxLang source code consistent. It helps teams apply the same style across files and editors.

Formatting support runs through the same language tooling stack. That keeps editor behavior predictable.

### Configuration file schemas

Language tools also support project configuration files. This makes settings easier to discover and validate.

Important files include:

* `.bxlint.json` for diagnostics configuration
* `boxlang.json` for mappings, class paths, and modules
* `boxlang.lsp.*` workspace settings in the IDE

Schema support improves validation, autocomplete, and editor guidance.

### Editor support

Any editor with an LSP client can connect to the BoxLang language server. The most complete integration today is the [VSCode overview](/vscode/overview.md).

That gives BoxLang a shared foundation for editor tooling while keeping each client lightweight.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://boxlang-ide.ortusbooks.com/language-tools/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.