<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>xlens blog</title><description>Engineering notes, guides and announcements from the xlens team.</description><link>https://xlens.dev/</link><item><title>Using xlens from Claude Code via MCP</title><link>https://xlens.dev/blog/xlens-from-claude-code/</link><guid isPermaLink="true">https://xlens.dev/blog/xlens-from-claude-code/</guid><description>Let your coding agent list production issues, read the evidence and the source, fix them, and report back.</description><pubDate>Tue, 24 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Verifying a fix with a one-sided z-test</title><link>https://xlens.dev/blog/verifying-fixes-with-a-z-test/</link><guid isPermaLink="true">https://xlens.dev/blog/verifying-fixes-with-a-z-test/</guid><description>Passing CI shows that a fix builds, not that it works. How xlens compares issue rates across builds to decide.</description><pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Why analytics should read your source</title><link>https://xlens.dev/blog/analytics-should-read-your-source/</link><guid isPermaLink="true">https://xlens.dev/blog/analytics-should-read-your-source/</guid><description>A dead click in a dashboard is a mystery. A dead click at Cart.tsx:45 is a ticket. On mapping behaviour back to code.</description><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Introducing xlens</title><link>https://xlens.dev/blog/introducing-xlens/</link><guid isPermaLink="true">https://xlens.dev/blog/introducing-xlens/</guid><description>Product analytics that starts from your source code, finds what&apos;s broken in real sessions, and opens the pull request that fixes it.</description><pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate></item></channel></rss>