<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Trainer on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/trainer/</link><description>Recent content in Trainer on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 06 Nov 2025 22:00:00 +0530</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/trainer/index.xml" rel="self" type="application/rss+xml"/><item><title>Core Concepts: Agents, Trainers, and the Lightning Server</title><link>https://ai-blog.noorshomelab.dev/agentic-lightening-guide/core-concepts-agents-trainers-and-the-lightning-server/</link><pubDate>Thu, 06 Nov 2025 22:00:00 +0530</pubDate><guid>https://ai-blog.noorshomelab.dev/agentic-lightening-guide/core-concepts-agents-trainers-and-the-lightning-server/</guid><description>&lt;h2 id="core-concepts-agents-trainers-and-the-lightning-server"&gt;Core Concepts: Agents, Trainers, and the Lightning Server&lt;/h2&gt;
&lt;p&gt;Now that you have your environment set up, let&amp;rsquo;s explore the foundational concepts and key components that make Agentic Lightening so powerful. Understanding these building blocks is crucial for effectively leveraging the framework.&lt;/p&gt;
&lt;p&gt;Agentic Lightening operates on a client-server architecture, enabling the decoupling of your agent&amp;rsquo;s execution logic from the optimization process. The main actors in this system are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;LitAgent&lt;/code&gt; (The Agent Client):&lt;/strong&gt; Your AI agent, often built with another framework, wrapped to interact with the Lightening system.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;AgentLightningServer&lt;/code&gt; (The Server):&lt;/strong&gt; A central hub that manages tasks, resources, and orchestrates the training loop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;Trainer&lt;/code&gt; (The Optimization Engine):&lt;/strong&gt; The component that runs the training algorithms, leveraging data from &lt;code&gt;LitAgent&lt;/code&gt; instances via the &lt;code&gt;AgentLightningServer&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;LightningStore&lt;/code&gt;:&lt;/strong&gt; A central repository (often backed by a database) that holds tasks, resources, and traces, facilitating the feedback loop.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Let&amp;rsquo;s break down each of these in detail.&lt;/p&gt;</description></item></channel></rss>