<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Windsurf on My Blog</title><link>https://hugo-blog.aitbytes.dev/tags/windsurf/</link><description>Recent content in Windsurf on My Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 11 Jun 2026 11:00:00 +0000</lastBuildDate><atom:link href="https://hugo-blog.aitbytes.dev/tags/windsurf/index.xml" rel="self" type="application/rss+xml"/><item><title>We Compared 6 AI Coding Tools on Security. The Gap Between #1 and #2 Is Alarming.</title><link>https://hugo-blog.aitbytes.dev/posts/2026-06-11-agentic-coding-tools-security-comparison/</link><pubDate>Thu, 11 Jun 2026 11:00:00 +0000</pubDate><guid>https://hugo-blog.aitbytes.dev/posts/2026-06-11-agentic-coding-tools-security-comparison/</guid><description>&lt;p&gt;One tool has 50 admin-controlled security settings deployable via MDM. Two tools have literally no documented MCP governance at all. One tool can&amp;rsquo;t even let admins disable telemetry.&lt;/p&gt;
&lt;p&gt;I spent two weeks digging through every piece of public documentation across six agentic coding tools — not marketing pages, not whitepapers, but actual config files, API docs, privacy policies, and security certifications. What I found was a landscape where the distance between best-in-class and &amp;ldquo;we&amp;rsquo;ll figure it out later&amp;rdquo; is measured in light-years, not inches.&lt;/p&gt;</description></item></channel></rss>