<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>claude on My Blog</title>
    <link>https://npatta01.github.io/categories/claude/</link>
    <description>Recent content in claude on My Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 29 Mar 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://npatta01.github.io/categories/claude/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Claude Code Tracing</title>
      <link>https://npatta01.github.io/post/2026/03/claude-code-tracing/</link>
      <pubDate>Sun, 29 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://npatta01.github.io/post/2026/03/claude-code-tracing/</guid>
      <description>&lt;p&gt;Tracing Claude Code is useful when you want to inspect prompts, understand tool usage, or keep an eye on cost. The three approaches I use most are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;claude-code-logger&lt;/code&gt; for full request and response inspection&lt;/li&gt;
&lt;li&gt;Arize&amp;rsquo;s &lt;code&gt;claude-code-tracing&lt;/code&gt; plugin for Phoenix traces&lt;/li&gt;
&lt;li&gt;OpenRouter for hosted usage visibility and cost tracking&lt;/li&gt;
&lt;/ol&gt;</description>
    </item>
    
  </channel>
</rss>