<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kanbots: AI Agents, Worktrees, &amp; Dev Workflows on AI VOID</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/</link><description>Recent content in Kanbots: AI Agents, Worktrees, &amp; Dev Workflows on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up Your Kanbots Workshop: Tauri v2 and Svelte 5</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/setup-kanbots-tauri-svelte/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/setup-kanbots-tauri-svelte/</guid><description>&lt;p&gt;Welcome to the Kanbots project, where we&amp;rsquo;ll build an innovative desktop Kanban application designed to host and orchestrate multiple AI agents. This application will empower you to automate development tasks, from code generation to review, leveraging isolated Git worktrees for each agent&amp;rsquo;s context.&lt;/p&gt;
&lt;p&gt;In this first chapter, we lay the groundwork for Kanbots. We&amp;rsquo;ll set up the core cross-platform desktop application using Tauri v2 for the backend and Rust, paired with a modern Svelte 5 frontend. By the end of this milestone, you will have a functional desktop application window displaying a basic Svelte interface, ready for further development. This foundational setup is crucial for enabling the local-first, privacy-conscious AI agent interactions that will define Kanbots.&lt;/p&gt;</description></item><item><title>Building the Core Kanban Board UI</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/build-kanban-board-ui/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/build-kanban-board-ui/</guid><description>&lt;p&gt;In this chapter, we&amp;rsquo;re laying the visual and interactive groundwork for Kanbots: a functional Kanban board. This isn&amp;rsquo;t just about pretty pixels; it&amp;rsquo;s about creating the canvas where our AI agents will operate. By the end of this milestone, you will have a desktop application with a fully interactive Kanban board, allowing you to add, edit, and move task cards between columns. This core UI is essential for managing the AI-driven development tasks we&amp;rsquo;ll introduce later.&lt;/p&gt;</description></item><item><title>Mastering Git Worktrees for Isolated Agent Tasks</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/mastering-git-worktrees/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/mastering-git-worktrees/</guid><description>&lt;h2 id="isolated-development-with-git-worktrees"&gt;Isolated Development with Git Worktrees&lt;/h2&gt;
&lt;p&gt;Imagine a team of highly efficient AI developers, each working on a separate feature branch, but all within the same repository, without ever stepping on each other&amp;rsquo;s toes. This is the power we&amp;rsquo;re bringing to Kanbots in this chapter. We&amp;rsquo;ll enable each Kanban card to spawn and manage its own isolated Git environment using &lt;strong&gt;Git worktrees&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This milestone is critical because AI agents, especially those generating code, need a clean, predictable workspace. Without isolation, concurrent agents could overwrite each other&amp;rsquo;s changes, leading to chaos and unpredictable outcomes. Git worktrees provide this crucial sandboxing, allowing agents to operate in parallel, each with its own working directory and branch, while still sharing the underlying repository history and objects.&lt;/p&gt;</description></item><item><title>Integrating Your First AI Agent: Claude Code or Codex</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/integrate-first-ai-agent/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/integrate-first-ai-agent/</guid><description>&lt;p&gt;This chapter marks a pivotal moment for Kanbots. We&amp;rsquo;re moving beyond a static Kanban board and injecting intelligence by integrating our first AI agent. You&amp;rsquo;ll learn how to connect an AI model like Claude Code or a modern OpenAI equivalent (e.g., GPT-4o) to a Kanban card. This enables the agent to perform specific tasks, such as generating code, within its dedicated git worktree. By the end of this milestone, your Kanbots application will be able to dispatch a task to an AI agent, have that agent generate content (like a simple code file), and observe the results directly within the isolated worktree associated with your Kanban card. This lays the foundation for powerful, automated development workflows.&lt;/p&gt;</description></item><item><title>Orchestrating Multi-Agent Workflows with Personas</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/orchestrate-multi-agent-workflows/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/orchestrate-multi-agent-workflows/</guid><description>&lt;p&gt;In the previous chapters, you&amp;rsquo;ve built a foundational Kanban board, integrated Git worktrees for isolated task contexts, and even enabled a single AI agent to perform basic tasks. This chapter marks a significant step forward: &lt;strong&gt;orchestrating multiple AI agents to collaborate on a single task, each with a distinct persona.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This milestone is critical because real-world development often involves multiple roles and handoffs. By simulating this with AI agents, we move beyond simple task automation towards a more intelligent, autonomous development assistant. By the end of this chapter, your Kanbots application will be able to initiate and manage sequential workflows, demonstrating how different AI &amp;ldquo;personalities&amp;rdquo; can contribute to a larger goal. You&amp;rsquo;ll verify the workflow by observing agents making distinct, persona-aligned changes in a Git worktree, ultimately completing a small feature or refactoring task.&lt;/p&gt;</description></item><item><title>Real-time Agent Progress and User Control UI</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/realtime-agent-ui-control/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/realtime-agent-ui-control/</guid><description>&lt;p&gt;Interacting with AI agents can often feel like giving a command to a black box. You trigger a task, wait, and eventually, an output appears. For a multi-agent system like Kanbots, this lack of transparency can lead to frustration and inefficiency. This chapter addresses that challenge by equipping our Kanbots application with real-time feedback and user controls.&lt;/p&gt;
&lt;p&gt;By the end of this milestone, your Kanbots application will provide a dynamic interface that displays agent progress, streams logs, and allows users to pause, resume, or cancel agent tasks directly from the Kanban board. This dramatically improves the user experience, giving operators crucial insights and control over complex AI workflows.&lt;/p&gt;</description></item><item><title>Securing API Keys and Robust Error Handling</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/secure-api-keys-error-handling/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/secure-api-keys-error-handling/</guid><description>&lt;p&gt;In this chapter, we elevate Kanbots from a functional prototype to a more robust, production-minded application. We&amp;rsquo;ll tackle two critical aspects: the secure management of sensitive AI API keys and the implementation of comprehensive error handling and logging. These elements are non-negotiable for any application that interacts with external services or handles user data, ensuring both security and a smooth user experience.&lt;/p&gt;
&lt;p&gt;By the end of this milestone, your Kanbots application will no longer store API keys in plain text or crash silently. Instead, it will securely load credentials, gracefully handle expected and unexpected failures from AI agents or Git operations, and provide clear feedback to the user and logs for debugging. This significantly improves the application&amp;rsquo;s reliability, maintainability, and trustworthiness.&lt;/p&gt;</description></item><item><title>Logging Agent Activities and Deployment Considerations</title><link>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/logging-deployment-considerations/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/kanbots-ai-worktrees-2026/logging-deployment-considerations/</guid><description>&lt;p&gt;Debugging and understanding the behavior of a multi-agent system like Kanbots can be incredibly challenging without proper visibility. In this final chapter, we&amp;rsquo;ll equip our Kanbots application with robust logging capabilities to capture agent activities, inputs, outputs, and any errors. This provides the essential observability needed to diagnose issues, track performance, and even audit AI agent decisions.&lt;/p&gt;
&lt;p&gt;Beyond observability, this chapter also guides you through the critical steps of preparing your Kanbots application for distribution. We&amp;rsquo;ll explore Tauri&amp;rsquo;s deployment features, focusing on how to package your application for various operating systems and important considerations like secure API key management and application signing.&lt;/p&gt;</description></item></channel></rss>