<?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: GUSTAVOSIS</title>
    <description>The latest articles on DEV Community by GUSTAVOSIS (@gustavosis).</description>
    <link>https://dev.to/gustavosis</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%2F4112916%2F291fec6a-285c-4380-9cc3-e8366f518c2a.jpg</url>
      <title>DEV Community: GUSTAVOSIS</title>
      <link>https://dev.to/gustavosis</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gustavosis"/>
    <language>en</language>
    <item>
      <title>Why I’m building an AI coding runtime that doesn’t depend on one model</title>
      <dc:creator>GUSTAVOSIS</dc:creator>
      <pubDate>Mon, 07 Sep 2026 00:02:41 +0000</pubDate>
      <link>https://dev.to/gustavosis/why-im-building-an-ai-coding-runtime-that-doesnt-depend-on-one-model-3k0a</link>
      <guid>https://dev.to/gustavosis/why-im-building-an-ai-coding-runtime-that-doesnt-depend-on-one-model-3k0a</guid>
      <description>&lt;p&gt;AI coding tools are getting better very fast, but there’s one architectural decision I don’t really like: most of them are deeply tied to a specific model, provider, or workflow.&lt;/p&gt;

&lt;p&gt;That works well while that model is the best option.&lt;/p&gt;

&lt;p&gt;But models change constantly.&lt;/p&gt;

&lt;p&gt;One month one provider is ahead, then another gets cheaper, local models improve, pricing changes, limits change, and suddenly your whole workflow is attached to a different stack.&lt;/p&gt;

&lt;p&gt;That’s the problem I’m trying to solve with Airuncode.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fszof5s3yu5ewrk636aok.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fszof5s3yu5ewrk636aok.png" alt=" " width="800" height="432"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbtff7ol7fpgic8faqvup.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbtff7ol7fpgic8faqvup.png" alt=" " width="800" height="432"&gt;&lt;/a&gt;``&lt;br&gt;
The idea is simple:&lt;/p&gt;

&lt;p&gt;The runtime should stay stable. The model should be replaceable.&lt;/p&gt;

&lt;p&gt;Airuncode runs locally and acts as the execution layer around the agent. The model is just one component of that system.&lt;/p&gt;

&lt;p&gt;So instead of rebuilding your workflow around each provider, the runtime handles things like:&lt;/p&gt;

&lt;p&gt;project files&lt;br&gt;
terminal access&lt;br&gt;
git&lt;br&gt;
tests&lt;br&gt;
execution&lt;br&gt;
agent orchestration&lt;br&gt;
context&lt;br&gt;
provider switching&lt;/p&gt;

&lt;p&gt;You can use cloud models, your own API keys, or local models depending on the task.&lt;/p&gt;

&lt;p&gt;I think this matters because developers are going to use multiple models, not one.&lt;/p&gt;

&lt;p&gt;Maybe you want a frontier model for architecture, a cheaper model for repetitive work, and a local model when privacy or cost matters.&lt;/p&gt;

&lt;p&gt;The workflow shouldn’t have to change every time.&lt;/p&gt;

&lt;p&gt;I’m also experimenting with a second idea inside Airuncode called V-CORE.&lt;/p&gt;

&lt;p&gt;Instead of asking an AI agent to recreate rendering, physics, terrain, animation, and other low-level systems from scratch, V-CORE gives the agent native capabilities it can build on top of.&lt;/p&gt;

&lt;p&gt;That leads to a broader question I’m interested in:&lt;/p&gt;

&lt;p&gt;How much of an agent’s capability comes from the model, and how much comes from the runtime and tools around it?&lt;/p&gt;

&lt;p&gt;My suspicion is that the runtime matters much more than people currently give it credit for.&lt;/p&gt;

&lt;p&gt;Airuncode is already usable, and I’m building it in public:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://airuncode.com" rel="noopener noreferrer"&gt;https://airuncode.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d especially like feedback from people using Cursor, Claude Code, Codex, OpenCode or local models every day.&lt;/p&gt;

&lt;p&gt;Do you actually want model independence, or would you rather use a coding agent that is deeply optimized around one provider?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>coding</category>
      <category>development</category>
    </item>
  </channel>
</rss>
