<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ToolServer on Defender TD5</title><link>https://td5.390er.de/kategorien/toolserver/</link><description>Recent content in ToolServer on Defender TD5</description><generator>Hugo</generator><language>de</language><lastBuildDate>Tue, 18 Aug 2026 08:47:17 +0200</lastBuildDate><atom:link href="https://td5.390er.de/kategorien/toolserver/index.xml" rel="self" type="application/rss+xml"/><item><title>How AppleBridge Uses Apple Events: A Beginner's Guide with Examples</title><link>https://td5.390er.de/applebridge/how-applebridge-uses-apple-events-a-beginner-s-guide-with-examples/</link><pubDate>Tue, 18 Aug 2026 08:42:11 +0200</pubDate><guid>https://td5.390er.de/applebridge/how-applebridge-uses-apple-events-a-beginner-s-guide-with-examples/</guid><description>&lt;p&gt;Apple Events are the classic Macintosh&amp;rsquo;s way of letting one program send a structured message to another and get a reply back. AppleBridge leans on exactly this mechanism for one specific job: running commands on the emulated Mac and capturing their output. This guide explains how that works, why it matters, and how to try it yourself — starting gently and building up.&lt;/p&gt;
&lt;h2 id="the-one-paragraph-mental-model"&gt;The one-paragraph mental model&lt;/h2&gt;
&lt;p&gt;When you ask Claude (or type a raw command into the bridge) to run something like &lt;code&gt;Echo 'Hello'&lt;/code&gt; on the Mac, the request travels from the host into the guest over TCP. Inside the guest, the AppleBridge daemon does &lt;strong&gt;not&lt;/strong&gt; run the command itself. It packages the command as an Apple Event and hands it to a separate program — &lt;strong&gt;ToolServer&lt;/strong&gt; — that knows how to execute MPW commands. ToolServer runs it, then sends the results &lt;em&gt;back&lt;/em&gt; to the daemon inside the Apple Event&amp;rsquo;s &lt;strong&gt;reply&lt;/strong&gt;. The daemon streams that reply out to the host. That round trip — event out, reply back — is the whole idea.&lt;/p&gt;</description></item></channel></rss>