docs: Add LSP prioritization guidance for project CLAUDE.md#80
docs: Add LSP prioritization guidance for project CLAUDE.md#80kevinold wants to merge 2 commits intoEveryInc:mainfrom
Conversation
Add "Customizing Agent Behavior" section to README with example CLAUDE.md snippets that projects can use to prioritize LSP tools over grep for code understanding. Includes both minimal (one-line) and detailed versions, plus guidance on when LSP vs grep is appropriate. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Move documentSymbol to first position with "(ALWAYS START HERE)" - Add Agent Delegation section with sub-agent instruction - Add "(MANDATORY)" emphasis to header - Include Rust in supported languages - Add sub-agent awareness in introduction 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
Thanks! Should we just reach for LSPs instead of grep either way? If so, maybe we can bake it into the main loop? Curious to hear what you think and how it works for you. |
|
Honestly I’m still testing this. It hasn’t returned the value I’d hoped and I’m not sure if it is the updates or Claude Code shipping flakiness with updates around this. IMHO we should aim to ship both, detect LSPs and use them and fallback to grep. And there are several situations where grep is the answer, so it’s not an either/or, but both/and with preference to LSP if available. I will keep testing this and following up this week. On Jan 20, 2026, at 6:36 PM, Kieran Klaassen ***@***.***> wrote:kieranklaassen left a comment (EveryInc/compound-engineering-plugin#80)
Thanks! Should we just reach for LSPs instead of grep either way? If so, maybe we can bake it into the main loop? Curious to hear what you think and how it works for you.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Hows this working? I still prefer to make the main plugin better than just adding docs. Hows this worikgn for you |
|
Thanks for the thoughtful write-up on LSP prioritization! This overlaps with #124 which adds a formal setup/config system. We're going to hold off on both for now while we think through the right approach to project-level customization. Appreciate the contribution! |
|
Yea I haven't seen it engaging much honestly with LSP, so I defer to your judgement on this. Maybe we close this and pursue another option? |
|
Thanks for this contribution! We're going to close this in favor of making the LSP prioritization work directly in the agents rather than requiring users to add documentation to their CLAUDE.md. Appreciate the idea though — the opt-in approach is solid thinking. |
Summary
Context
Instead of modifying plugin agents to prioritize LSP, this approach lets projects opt-in by adding guidance to their own CLAUDE.md. This is cleaner because:
Test plan