microsoft / microsoft/multilspy

FYI - we used multispy in an AI Agent project

Open
#100 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
610
Forks
111
PR merge metrics
No merged PRs in 30d

Description

Dear @LakshyAAAgrawal and all other multilspy contributors,

First, I'd like to personally thank you for this amazing project! From all LSP related things implemented in python this is the best one I have seen, and by a large margin.

I wanted to tell you that we built an AI Coding Agent (in fact, an MCP Server that can act as a coding agent) by heavily relying on multilspy. In fact, without multilspy we might not even have started it.

Unfortunately, it would have been impractical for us to use multilspy as dependency, since we had to significantly expand the language server's symbolic capabilities (far beyond standard LSP) to achieve our goals. So instead, we reluctantly copied the source code. We were also not sure you would be interested in integrating our extensions into the official multilspy, since they have quite a different focus and scope.

If you are interested in it, we would be happy to start the conversation about integrating our changes into your project and maybe eventually including multilspy as dependency instead of as copied code.

Meanwhile, we will keep porting the extensions of this repo to our copy. Do you have a preference for how to acknowledge the work of the contributors? We won't be able to cherry-pick, but we could for example mention their names in the commits.

Maybe some of the contributors here would also be interested in contributing to our project :)

In any case, thanks again for the really well written and functional code here!

You'll find our project here:
https://github.com/oraios/serena

@opcode81 FYI

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing this issue and the referenced Serena project to understand the copied multilspy extensions and the proposed integration. There are no files or tests identified. Done would require an agreed scope for integrating the extensions and a decision on dependency use and contributor attribution.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.