<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jailbreaking on MacWorks</title><link>https://macworks.dev/tags/jailbreaking/</link><description>Recent content in Jailbreaking on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/jailbreaking/index.xml" rel="self" type="application/rss+xml"/><item><title>2026-06-16</title><link>https://macworks.dev/docs/week/simonwillison/simonwillison-2026-06-16/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/week/simonwillison/simonwillison-2026-06-16/</guid><description>&lt;h1 id="simon-willison--2026-06-16"&gt;Simon Willison — 2026-06-16&lt;a class="anchor" href="#simon-willison--2026-06-16"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="highlight"&gt;Highlight&lt;a class="anchor" href="#highlight"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The meatiest topic today is Simon&amp;rsquo;s sharp criticism of the export controls placed on Claude Fable 5. He connects the dots between a press report and security expert Katie Moussouris to point out the absurdity of penalizing an AI model for successfully fixing security vulnerabilities, which is a core feature of cyberdefense.&lt;/p&gt;
&lt;h2 id="posts"&gt;Posts&lt;a class="anchor" href="#posts"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="https://simonwillison.net/2026/Jun/16/fable-5-export-controls/#atom-everything"&gt;The Fable 5 Export Controls Harm US Cyber Defense&lt;/a&gt;&lt;/strong&gt;
Simon strongly criticizes the US export controls placed on Claude Fable 5, citing security expert Katie Moussouris. The so-called &amp;ldquo;jailbreak&amp;rdquo; that triggered the ban was merely researchers asking the model to &amp;ldquo;fix this code&amp;rdquo; after it had refused a prompt to &amp;ldquo;review the code for security issues&amp;rdquo;. Simon argues that banning models for executing the &amp;ldquo;find, fix, and test loop&amp;rdquo; fundamentally misunderstands how AI assists in defensive security, effectively penalizing a model for fixing bugs.&lt;/p&gt;</description></item><item><title>2026-06-15</title><link>https://macworks.dev/docs/week/simonwillison/simonwillison-2026-06-15/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/week/simonwillison/simonwillison-2026-06-15/</guid><description>&lt;h1 id="simon-willison--2026-06-15"&gt;Simon Willison — 2026-06-15&lt;a class="anchor" href="#simon-willison--2026-06-15"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="highlight"&gt;Highlight&lt;a class="anchor" href="#highlight"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The most exciting update today is the release of &lt;code&gt;datasette-agent 0.3a0&lt;/code&gt;, which introduces natural language database modification right from the terminal. By combining the new &lt;code&gt;execute_write_sql&lt;/code&gt; tool with an &lt;code&gt;--unsafe&lt;/code&gt; auto-approval mode, Simon has made it possible to chat directly with a SQLite database and modify its schema and records on the fly.&lt;/p&gt;
&lt;h2 id="posts"&gt;Posts&lt;a class="anchor" href="#posts"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="https://simonwillison.net/2026/Jun/15/datasette-agent/#atom-everything"&gt;datasette-agent 0.3a0&lt;/a&gt;&lt;/strong&gt; · Source
Simon just shipped a major update to his experimental &lt;code&gt;datasette-agent&lt;/code&gt; project, adding an &lt;code&gt;execute_write_sql&lt;/code&gt; tool that can prompt for user approval before writing to a database. He also enhanced the CLI chat terminal with options like &lt;code&gt;--yes&lt;/code&gt;, &lt;code&gt;--root&lt;/code&gt;, and &lt;code&gt;--unsafe&lt;/code&gt; to streamline or bypass these permission checks entirely. Using the &lt;code&gt;--unsafe&lt;/code&gt; flag alongside a model like &lt;code&gt;gpt-5.5&lt;/code&gt;, developers can now converse directly with a specific database to execute structural changes, such as creating tables or inserting records via natural language.&lt;/p&gt;</description></item></channel></rss>