<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Agents on mhbxyz.me</title><link>https://mhbxyz.github.io/en/tags/ai-agents/</link><description>Recent content in AI Agents on mhbxyz.me</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 13 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mhbxyz.github.io/en/tags/ai-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>protonmail-mcp: give an agent email access without a blank check</title><link>https://mhbxyz.github.io/en/articles/protonmail-mcp-give-an-agent-email-access-with-limits/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://mhbxyz.github.io/en/articles/protonmail-mcp-give-an-agent-email-access-with-limits/</guid><description>&lt;h2 id="an-email-is-untrusted-input"&gt;An email is untrusted input&lt;/h2&gt;
&lt;p&gt;Asking an agent to summarize your messages is useful. But other people wrote those messages. A sender can place instructions in one, telling the agent to send data elsewhere, delete a message, or ignore the original request. Giving the agent unrestricted mailbox access can turn a reading task into a risk of unintended action.&lt;/p&gt;
&lt;p&gt;I built &lt;a href="https://github.com/mhbxyz/protonmail-mcp"&gt;protonmail-mcp&lt;/a&gt; around this boundary. The server connects an MCP client to Proton Mail through Proton Bridge, which exposes IMAP and SMTP locally. It offers specific tools to the agent instead of allowing arbitrary IMAP or SMTP commands.&lt;/p&gt;</description></item><item><title>Make a repository usable by a development agent</title><link>https://mhbxyz.github.io/en/articles/agentic-engineering-wiki-make-a-repository-usable-by-an-agent/</link><pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate><guid>https://mhbxyz.github.io/en/articles/agentic-engineering-wiki-make-a-repository-usable-by-an-agent/</guid><description>&lt;h2 id="the-repository-should-explain-how-to-work"&gt;The repository should explain how to work&lt;/h2&gt;
&lt;p&gt;An agent can read code, but that does not tell it which command runs the tests, which migrations are sensitive, or what counts as finished work. A human joining the project asks the same questions. In &lt;a href="https://github.com/mhbxyz/agentic-engineering-wiki"&gt;Agentic Engineering Wiki&lt;/a&gt;, I collected a way to make those answers visible in the repository.&lt;/p&gt;
&lt;p&gt;The starting point is modest: a short &lt;code&gt;AGENTS.md&lt;/code&gt; and stable project commands. The first states the constraints; the second makes them verifiable. Adding integrations before these basics mainly creates more ways to make a mistake.&lt;/p&gt;</description></item><item><title>Remotion Agent Starter: describe a video edit with a manifest</title><link>https://mhbxyz.github.io/en/articles/remotion-agent-starter-video-editing-with-a-manifest/</link><pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate><guid>https://mhbxyz.github.io/en/articles/remotion-agent-starter-video-editing-with-a-manifest/</guid><description>&lt;h2 id="an-edit-you-can-review"&gt;An edit you can review&lt;/h2&gt;
&lt;p&gt;When an edit is just a series of clicks in an interface, it is hard to tell what changed between two versions. It is harder still to ask an agent to adjust one scene without touching everything else. With &lt;a href="https://github.com/mhbxyz/remotion-agent-starter"&gt;Remotion Agent Starter&lt;/a&gt;, I wanted to put routine editorial decisions in a JSON manifest that can be read, checked, and versioned.&lt;/p&gt;
&lt;p&gt;The manifest describes scenes, durations, media, and transitions. React and Remotion handle rendering. The separation is simple: data says &lt;strong&gt;what&lt;/strong&gt; to edit; components decide &lt;strong&gt;how&lt;/strong&gt; each frame looks.&lt;/p&gt;</description></item></channel></rss>