<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ellugia</title>
    <description>The latest articles on DEV Community by ellugia (@ellugia).</description>
    <link>https://dev.to/ellugia</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4127999%2F9c40bd5d-e673-43da-8f7e-e997ad200916.png</url>
      <title>DEV Community: ellugia</title>
      <link>https://dev.to/ellugia</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ellugia"/>
    <language>en</language>
    <item>
      <title>CodeScope: Use Your ChatGPT Quota to Understand Local Repositories</title>
      <dc:creator>ellugia</dc:creator>
      <pubDate>Wed, 16 Sep 2026 12:07:41 +0000</pubDate>
      <link>https://dev.to/ellugia/codescope-use-your-chatgpt-quota-to-understand-local-repositories-8c1</link>
      <guid>https://dev.to/ellugia/codescope-use-your-chatgpt-quota-to-understand-local-repositories-8c1</guid>
      <description>&lt;p&gt;I wanted to use the ChatGPT quota I already have for repository questions, without turning every exploratory step into a coding-agent task.&lt;/p&gt;

&lt;p&gt;That is the reason I built CodeScope.&lt;/p&gt;

&lt;p&gt;CodeScope is a local, read-only MCP bridge that lets an MCP-compatible chat inspect the repositories you explicitly choose on your computer.&lt;/p&gt;

&lt;p&gt;The idea is simple: use the quota from ordinary ChatGPT conversations for code exploration, while keeping Codex or other coding-agent capacity available for implementation work.&lt;/p&gt;

&lt;h2&gt;
  
  
  What CodeScope does
&lt;/h2&gt;

&lt;p&gt;CodeScope gives an MCP-compatible chat a controlled way to understand selected repositories:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;read files from configured repositories&lt;/li&gt;
&lt;li&gt;inspect Git history and repository status&lt;/li&gt;
&lt;li&gt;keep the accessible repositories in an explicit local allowlist&lt;/li&gt;
&lt;li&gt;work locally through the standard MCP connection&lt;/li&gt;
&lt;li&gt;keep repository access read-only by design&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The bridge does not expose commits, checkout, reset, arbitrary filesystem paths, or a general-purpose command shell. It only works with repositories that the user explicitly configures.&lt;/p&gt;

&lt;h2&gt;
  
  
  Install
&lt;/h2&gt;

&lt;p&gt;The recommended installation is global:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;--global&lt;/span&gt; @ellugia/codescope
codescope setup
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The setup wizard creates the local configuration, lets you choose the repositories that CodeScope can access, and guides you through connecting it to your MCP client.&lt;/p&gt;

&lt;p&gt;A project-local installation is also available:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install&lt;/span&gt; @ellugia/codescope
npx codescope setup
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once it is configured, you can ask questions such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where is authentication connected?&lt;/li&gt;
&lt;li&gt;Which modules call this function?&lt;/li&gt;
&lt;li&gt;What changed in the last five commits?&lt;/li&gt;
&lt;li&gt;How is this repository organized?&lt;/li&gt;
&lt;li&gt;Which files are involved in this feature?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is to make repository exploration feel like a normal conversation, while keeping the actual files on the user’s own computer and the accessible scope explicit.&lt;/p&gt;

&lt;p&gt;CodeScope is open source and released under the MIT license.&lt;/p&gt;

&lt;p&gt;It was built primarily with ChatGPT 5.6 Luna Max, followed by manual review, integration testing, and security checks.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/ellugia/codescope" rel="noopener noreferrer"&gt;https://github.com/ellugia/codescope&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;npm: &lt;a href="https://www.npmjs.com/package/@ellugia/codescope" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/@ellugia/codescope&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you use ChatGPT, Codex, or another MCP-compatible client to understand codebases, I would love to hear how you use this workflow and what would make it more useful.&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>opensource</category>
      <category>node</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
