<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agents on Michael S. Collier</title>
    <link>/tags/agents/</link>
    <description>Recent content in Agents on Michael S. Collier</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Michael S. Collier</copyright>
    <lastBuildDate>Thu, 27 Aug 2026 23:41:16 -0400</lastBuildDate>
    <atom:link href="/tags/agents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enabling WSL Support for the GitHub Copilot App</title>
      <link>/enabling-wsl-support-for-the-github-copilot-app/</link>
      <pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate>
      <guid>/enabling-wsl-support-for-the-github-copilot-app/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been intrigued by the &lt;a href=&#34;https://gh.io/app&#34;&gt;GitHub Copilot App&lt;/a&gt; ever since it first shipped at Build a few months ago. It offers a different way of working for me, and I&amp;rsquo;m getting more comfortable with it every day. One thing that held me back was its lack of support for repositories in WSL. That has now changed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bringing Build Home in Columbus</title>
      <link>/bringing-build-home-in-columbus/</link>
      <pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate>
      <guid>/bringing-build-home-in-columbus/</guid>
      <description>&lt;p&gt;Microsoft Build is always packed with big announcements, but my favorite part is bringing those ideas back home and figuring out what actually helps teams ship better software. On June 20th, we did exactly that at &lt;a href=&#34;https://developer.microsoft.com/en-us/reactor/events/27247/&#34;&gt;&lt;strong&gt;Microsoft Build \\localhost:columbus&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Build 2026 - Day 2</title>
      <link>/microsoft-build-2026-day-2/</link>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
      <guid>/microsoft-build-2026-day-2/</guid>
      <description>&lt;p&gt;Microsoft Build is a two-day event this year (after being three days in prior years).  That&amp;rsquo;s in line with the overall smaller Build - fewer attendees, smaller venue, and fewer days.  There was no day 2 keynote either.  For me, day 2 was full of breakout sessions, a hands-on lab, and great conversations with Microsoft and GitHub employees.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Build 2026 - Day 1</title>
      <link>/microsoft-build-2026-day-1/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>/microsoft-build-2026-day-1/</guid>
      <description>&lt;p&gt;I attended Microsoft Build in person on June 2, 2026. Below are my observations from day one. I’ll post a day-two update, as well as a wrap-up after the event.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Build 2025 Recap</title>
      <link>/microsoft-build-2025-recap/</link>
      <pubDate>Fri, 23 May 2025 00:00:00 +0000</pubDate>
      <guid>/microsoft-build-2025-recap/</guid>
      <description>&lt;p&gt;Microsoft Build 2025 centered on the future of intelligent agent-based applications. This post recaps my four-day experience in Seattle attending Build, covering keynotes, developer sessions, GitHub Copilot updates, .NET Aspire insights, and hands-on labs. Get a firsthand look at emerging trends and tools shaping how we build AI-powered solutions in the Microsoft ecosystem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
