<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Harsh Verma</title>
    <link>https://harshverma.com/</link>
    <description>Senior software engineer specializing in retrieval systems, AI evaluation, and production reliability.</description>
    <language>en</language>
    <atom:link href="https://harshverma.com/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Whole articles made a local model accurate, and 15× too slow</title>
      <link>https://harshverma.com/blog/2026-11-05-local-model-context-budget</link>
      <guid>https://harshverma.com/blog/2026-11-05-local-model-context-budget</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <description>On a local model, every 1,000 tokens of context costs ~2 s. Whole articles reach 0.59 correctness at ~160 s per answer; a context budget gets 0.49 at ~11 s, up from 0.36 with compact context. A frontier model scores 0.65 in 5 s.</description>
      <category>Latency</category>
      <category>Evals</category>
      <category>Local models</category>
      <category>Qwen3.8</category>
      <category>Retrieval</category>
      <category>RAG</category>
      <category>Langfuse</category>
    </item>
    <item>
      <title>MCP tool over a durable agent</title>
      <link>https://harshverma.com/blog/2026-10-19-mcp-tool-durable-agent</link>
      <guid>https://harshverma.com/blog/2026-10-19-mcp-tool-durable-agent</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>An MCP tool backed by Temporal workflows: agent runs survive worker crashes, stay within a hard USD cost budget, and work with OpenAI, Claude, or local models. End-to-end OpenTelemetry tracing with token and cost tracking.</description>
      <category>MCP</category>
      <category>Budget constraint</category>
      <category>Temporal</category>
      <category>Elasticsearch</category>
      <category>OpenTelemetry</category>
      <category>Langfuse</category>
    </item>
  </channel>
</rss>
