<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>tokenpatch Blog</title>
    <link>https://tokenpatch.com/blog</link>
    <description>AI coding cost optimization, DeepSeek executor workflows, and token savings articles.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>How to reduce AI coding costs without switching editors</title>
      <link>https://tokenpatch.com/blog/reduce-ai-coding-costs-without-switching-editors</link>
      <guid>https://tokenpatch.com/blog/reduce-ai-coding-costs-without-switching-editors</guid>
      <description>A practical workflow for reducing AI coding cost while keeping Codex, Claude Code, Cursor, or your existing agent in control.</description>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Using DeepSeek V4 Pro as a coding executor</title>
      <link>https://tokenpatch.com/blog/deepseek-v4-pro-coding-executor-workflow</link>
      <guid>https://tokenpatch.com/blog/deepseek-v4-pro-coding-executor-workflow</guid>
      <description>How tokenpatch uses DeepSeek V4 Pro for bounded implementation patches while the strong model keeps planning and review control.</description>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Request-level LLM cost is not enough for coding agents</title>
      <link>https://tokenpatch.com/blog/request-level-cost-vs-applied-patch-cost</link>
      <guid>https://tokenpatch.com/blog/request-level-cost-vs-applied-patch-cost</guid>
      <description>Why AI coding teams should measure cost per applied patch, not only request-level model usage.</description>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>