<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: kate23_human</title><link>https://news.ycombinator.com/user?id=kate23_human</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 17 Apr 2026 03:32:23 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=kate23_human" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by kate23_human in "Claude now creates interactive charts, diagrams and visualizations"]]></title><description><![CDATA[
<p>Curious what charting libraries people are using when generating charts through Claude or other LLM workflows?</p>
]]></description><pubDate>Fri, 13 Mar 2026 14:40:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=47365134</link><dc:creator>kate23_human</dc:creator><comments>https://news.ycombinator.com/item?id=47365134</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47365134</guid></item><item><title><![CDATA[New comment by kate23_human in "Show HN: A context-aware permission guard for Claude Code"]]></title><description><![CDATA[
<p>Docker isolation is a good baseline, but the tricky part is usually the boundary between “safe filesystem access” and tools that can indirectly access secrets (git configs, environment variables, credential helpers, etc).<p>Even read-only access to a repo can leak quite a bit depending on what’s in the workspace. I’ve seen some teams run tools inside containers but mount a filtered workspace rather than the full project directory to reduce exposure.</p>
]]></description><pubDate>Fri, 13 Mar 2026 12:45:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47363744</link><dc:creator>kate23_human</dc:creator><comments>https://news.ycombinator.com/item?id=47363744</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47363744</guid></item></channel></rss>