<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitHub Copilot on Uday K</title><link>https://uday.dev/tags/github-copilot/</link><description>Recent content in GitHub Copilot on Uday K</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 09 Aug 2026 11:15:02 -0400</lastBuildDate><atom:link href="https://uday.dev/tags/github-copilot/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Copilot + LSP: Smarter Code Context and Better Token Efficiency</title><link>https://uday.dev/posts/copilot-with-lsp/</link><pubDate>Sun, 09 Aug 2026 11:15:02 -0400</pubDate><guid>https://uday.dev/posts/copilot-with-lsp/</guid><description>&lt;p&gt;This guide walks through configuring Language Server Protocol (LSP) support for &lt;strong&gt;Go, Python, Ruby, TypeScript, and JavaScript&lt;/strong&gt; in GitHub Copilot CLI. It also includes practices for keeping AI coding sessions efficient and token-conscious.&lt;/p&gt;&#10;&lt;h2 id="part-of-a-series"&gt;Part of a Series&lt;/h2&gt;&#10;&lt;p&gt;This post is part of a broader series exploring how modern AI coding&#10;assistants understand and work with code.&lt;/p&gt;&#10;&lt;p&gt;The series starts with the foundations of how source code moves through the&#10;development toolchain—from &lt;strong&gt;ASTs and parsing to compilers and language&#10;servers (LSP)&lt;/strong&gt;—and then builds on those concepts to explain how AI coding&#10;tools can use this information to navigate and reason about a codebase.&lt;/p&gt;</description></item></channel></rss>