
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Fri, 14 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/plugin-system/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-14-trend-deepseek-harness-plugin-kernel.en</guid>
    <title>The Plugin Kernel Architecture of DeepSeek Harness — What Makes an Agent You Can Rewind</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-14-trend-deepseek-harness-plugin-kernel.en</link>
    <description>Harness, the open source coding agent DeepSeek released, makes the model, the tools, and even the UI into plugins. But the interesting part is not the word plugin. It is two design decisions: representing every execution as an append-only event log so that resume, fork, and replay all fall out of the same stream, and requiring plugins to undo their side effects when they are unloaded. This post works through what that structure makes possible, and why the old objection to plugin ecosystems still holds.</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai-agent</category><category>architecture</category><category>plugin-system</category><category>observability</category><category>open-source</category><category>hacker-news</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-14-trend-deepseek-harness-plugin-kernel.ja</guid>
    <title>DeepSeek Harnessのプラグインカーネル構造 — 巻き戻せるエージェントは何が違うのか</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-14-trend-deepseek-harness-plugin-kernel.ja</link>
    <description>DeepSeekが公開したオープンソースのコーディングエージェントHarnessは、モデルもツールもUIもすべてプラグインにした構造です。ただし実際に興味深いのはプラグインという言葉ではなく、2つの設計判断です。1つはすべての実行を追記専用のイベントログに残し、再開・分岐・再生を同じストリーム上で扱うこと、もう1つはプラグインを外すときに副作用を巻き戻すことを強制する点です。この構造が何を可能にするのか、そしてプラグイン生態系への古い反論がなぜ今も有効なのかを整理します。</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai-agent</category><category>architecture</category><category>plugin-system</category><category>observability</category><category>open-source</category><category>hacker-news</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-14-trend-deepseek-harness-plugin-kernel</guid>
    <title>DeepSeek Harness의 플러그인 커널 구조 — 되감을 수 있는 에이전트는 무엇이 다른가</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-14-trend-deepseek-harness-plugin-kernel</link>
    <description>DeepSeek이 공개한 오픈소스 코딩 에이전트 Harness는 모델도 도구도 UI도 전부 플러그인으로 만든 구조입니다. 그런데 실제로 흥미로운 부분은 플러그인이라는 단어가 아니라 두 가지 설계 결정입니다. 하나는 모든 실행을 추가 전용 이벤트 로그로 남겨 재개·분기·재생을 같은 스트림 위에서 처리한다는 것이고, 다른 하나는 플러그인 해제 시 부수 효과를 되돌리도록 강제한다는 것입니다. 이 구조가 무엇을 가능하게 하는지, 그리고 플러그인 생태계에 대한 오래된 반론이 왜 여전히 유효한지 정리합니다.</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ai-agent</category><category>architecture</category><category>plugin-system</category><category>observability</category><category>open-source</category><category>hacker-news</category>
  </item>

    </channel>
  </rss>
