can we let claude code actually use ty as an LSP?

claude code doesn't seem to know how to use ty as an LSP, I've tried to get it working in different ways, all using the latest claude code and the latest ty as of today, but nothing helps.

```
● Thanks for showing me the ty skill. So ty is available as a CLI type checker (via uv run ty check ... or uvx ty ...), and there's also a ty language server plugin configured for the editor.

Here's where I stand:

What I can do with ty:
- Run ty check via Bash to type-check files/directories
- Use it to catch type errors, validate code changes
- Configure rules in pyproject.toml / ty.toml

What I cannot do:
- I don't have native LSP tool integration (no goToDefinition, findReferences, workspaceSymbol, rename, etc. as callable tools)
- The ty language server runs in your editor (VS Code / IDE), not as something I can query interactively

So the CLAUDE.md instruction to "Use the ty python LSP over Grep/Glob/Read for code navigation" isn't something I can fulfill — I don't have LSP tools wired into my toolset. For code navigation (finding definitions, references, call
hierarchies), I'll use:

1. rg (ripgrep via Bash) for searching code — as instructed
2. fdfind via Bash for finding files — as instructed
3. Grep/Glob tools for pattern matching
4. ty check for type checking when validating changes

Would you like to update the CLAUDE.md to reflect what's actually available, or is there an LSP integration I'm missing?

```