<?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: Antonino Rizzo</title>
    <description>The latest articles on DEV Community by Antonino Rizzo (@antonino_rizzo_7f4c47607f).</description>
    <link>https://dev.to/antonino_rizzo_7f4c47607f</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%2F1805780%2Fc56432c5-5b04-4160-a67d-252a982fa8ba.jpg</url>
      <title>DEV Community: Antonino Rizzo</title>
      <link>https://dev.to/antonino_rizzo_7f4c47607f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/antonino_rizzo_7f4c47607f"/>
    <language>en</language>
    <item>
      <title>Building one open-source AI agent across CLI, Windows and Android</title>
      <dc:creator>Antonino Rizzo</dc:creator>
      <pubDate>Tue, 29 Sep 2026 16:54:23 +0000</pubDate>
      <link>https://dev.to/antonino_rizzo_7f4c47607f/building-one-open-source-ai-agent-across-cli-windows-and-android-m62</link>
      <guid>https://dev.to/antonino_rizzo_7f4c47607f/building-one-open-source-ai-agent-across-cli-windows-and-android-m62</guid>
      <description>&lt;p&gt;I’ve been building &lt;strong&gt;TALOS&lt;/strong&gt;, an open-source AI agent that I wanted to use in more than one environment.&lt;/p&gt;

&lt;p&gt;Instead of creating a separate product for every device, the goal became:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;one agent ecosystem, three interfaces: CLI, Windows Desktop and Android.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  TALOS CLI
&lt;/h2&gt;

&lt;p&gt;The CLI is the fastest way to use TALOS inside a development workflow.&lt;/p&gt;

&lt;p&gt;It can work with a project, read files, run tools, keep persistent conversations and use explicit permission modes before performing sensitive actions.&lt;/p&gt;

&lt;p&gt;Install it with:&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;-g&lt;/span&gt; talos-code
talos
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  TALOS Desktop
&lt;/h2&gt;

&lt;p&gt;The Windows application expands the same idea into a full workspace.&lt;/p&gt;

&lt;p&gt;It combines the agent with project files, a terminal, file review, Git/GitHub workflows, persistent sessions and model configuration.&lt;/p&gt;

&lt;p&gt;The goal is to keep the coding workflow inside one environment instead of constantly switching between an AI chat, terminal, editor and other tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  TALOS on Android
&lt;/h2&gt;

&lt;p&gt;Android is the part that originally pushed the project beyond being only a coding tool.&lt;/p&gt;

&lt;p&gt;TALOS can run compatible &lt;strong&gt;GGUF models directly on the phone through llama.cpp&lt;/strong&gt;, or connect to Ollama or cloud providers using your own API key.&lt;/p&gt;

&lt;p&gt;A local model can therefore run without sending the conversation to a TALOS server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Local-first by design
&lt;/h2&gt;

&lt;p&gt;TALOS does not require a TALOS account and does not include TALOS telemetry.&lt;/p&gt;

&lt;p&gt;You can choose between local models and external providers depending on the hardware and task.&lt;/p&gt;

&lt;p&gt;I also wanted actions to be explicit: tools operate through permissions, rather than giving the agent unrestricted access by default.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why build all three?
&lt;/h2&gt;

&lt;p&gt;CLI is great when you want speed.&lt;/p&gt;

&lt;p&gt;Desktop is better when you want visibility over files, tools and longer workflows.&lt;/p&gt;

&lt;p&gt;Android makes the agent available away from the development machine and makes local on-device inference possible.&lt;/p&gt;

&lt;p&gt;They solve different interaction problems, but I don’t think they need to be completely separate AI products.&lt;/p&gt;

&lt;p&gt;That is the experiment behind TALOS.&lt;/p&gt;

&lt;p&gt;The project is open source under &lt;strong&gt;AGPL-3.0&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Website:&lt;/strong&gt; &lt;a href="https://www.talos-code.com/" rel="noopener noreferrer"&gt;https://www.talos-code.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Source:&lt;/strong&gt; &lt;a href="https://github.com/Ninozzz95/talos" rel="noopener noreferrer"&gt;https://github.com/Ninozzz95/talos&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d especially like feedback from people building coding agents or running local LLMs:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What would you need to trust an agent enough to use it on a real project?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>cli</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
