Developer Tools
Code Intelligence
Plexon reads your project through a language server, the same one your editor uses. It answers about symbols instead of guessing from text, and it catches the mistakes it makes while it is still making them.
What happens in this clip
- Ask where a function is defined and who calls it. The answer comes from the project's own language server, not a text search.
- Ask what is broken right now and the current errors come back per file.
- Errors are re-checked after every edit the assistant makes.
- A setup script runs in a terminal inside the chat and asks its questions there.
- The assistant reads the prompt on screen and answers it.
Related features
The Compiler Answers, Not a Text Search
Search finds the letters you typed. A language server knows which of the four methods called Start you meant, that the reference in a comment is not a use, and that a call three packages away resolves here. Plexon starts the same server your editor would (gopls, pylsp, typescript-language-server, rust-analyzer) and puts the answer in the conversation, so a question about a symbol costs one lookup instead of reading five files to be sure.
- Definitions, references, implementations, and hover types and docs
- Call hierarchy in both directions: what calls this, and what this calls
- Every symbol a file declares, nested by what contains it
- Falls back to text search in a project no server covers
Ask By Name
Most tools of this kind want a file, a line, and a column, which means reading the file first just to count characters, and getting it wrong the moment anything shifts. Plexon takes the name. Ask about ProcessRequest and it resolves; say Server.Start when two types share a method name. When a name is genuinely ambiguous it lists the candidates and their positions rather than picking one and answering confidently about the wrong code.
- Name a symbol, or give a position, whichever you have
- Qualify with its container when a bare name is shared
- Ambiguity comes back as a list, never a silent guess
- Positions read the way an editor shows them, counting from one
Mistakes Surface While It Is Still Editing
When Plexon writes source code, it asks the language server what it now makes of that file and reads the answer back before moving on. A type that no longer lines up, an import that resolves nowhere, a call whose signature changed: it sees them on the edit that caused them and fixes them in the same reply, instead of leaving them for the next build.
- Errors sort ahead of warnings; editor hints stay out of it
- Only ever consults a server already running, so an edit never waits on a start-up
- Bounded per file and per batch, so a wide refactor stays quick
- Says when a verdict is still settling rather than presenting it as final
Nothing To Configure
Plexon works out the project language from what is in the folder, starts the server in the background, and installs it if it is missing and the toolchain to build it is there. The folder icon in the title bar carries the state. Until a server is ready, questions fall back to text search rather than waiting, and the first answer that can be precise is. Plugins can add servers for other languages, and enabling one takes effect immediately.
- Go, Python, TypeScript and JavaScript, and Rust out of the box
- Background install with a live state indicator, no prompts
- The project language stays warm; a server opened for a stray file is released once it goes quiet
- Plugins contribute more languages through a .lsp.json file
What it answers
Definition and references
Where a symbol comes from and everywhere it is used, resolved rather than matched.
Call hierarchy
What calls this, and what this calls, in one step each.
Implementations
What satisfies an interface or overrides a method.
File symbols
Everything a file declares, nested by what contains it.
Live diagnostics
What is broken in a file right now, and after every edit Plexon makes.
Name addressing
Ask about a symbol by name; no line and column numbers to look up.
Warm servers
Started in the background and kept ready, so answers come back fast.
No setup
Detected, installed, and started for you. Text search covers the rest.
Connects to
Nothing here works alone. See the whole map for how the pieces fit together.
What feeds it
Plugins extends this.
A plugin can contribute a language server for a language Plexon does not ship one for.
Where it goes
This feeds AI Chat & Modes.
Questions about a symbol are answered from the language server rather than from a text search.
This feeds Developer Tools.
Errors it introduces while editing come back with the edit, so they are fixed in the same reply.