<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>AI-Context-Window-한계 on gnosyslambda&#39;s log</title>
    <link>https://gnosyslambda.github.io/tags/ai-context-window-%ED%95%9C%EA%B3%84/</link>
    <description>Recent content in AI-Context-Window-한계 on gnosyslambda&#39;s log</description>
    <image>
      <title>gnosyslambda&#39;s log</title>
      <url>https://gnosyslambda.github.io/images/og-image.png</url>
      <link>https://gnosyslambda.github.io/images/og-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>ko-KR</language>
    <lastBuildDate>Sun, 05 Jul 2026 18:47:47 +0900</lastBuildDate>
    <atom:link href="https://gnosyslambda.github.io/tags/ai-context-window-%ED%95%9C%EA%B3%84/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI 코딩 도구 아키텍처와 운영 리스크</title>
      <link>https://gnosyslambda.github.io/posts/2026-07-05-ai-coding-tool-architecture-risks/</link>
      <pubDate>Sun, 05 Jul 2026 18:47:47 +0900</pubDate>
      <guid>https://gnosyslambda.github.io/posts/2026-07-05-ai-coding-tool-architecture-risks/</guid>
      <description>AI 코딩 도구를 만들 때 상태 저장, 컨텍스트 분리, API 호출 제어가 왜 중요한지 MV3와 PR 리뷰 자동화 사례로 정리합니다.</description>
    </item>
  </channel>
</rss>
