<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on madtea</title><link>https://madtea.lol/blog/</link><description>Recent content in Blog on madtea</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://madtea.lol/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing madtea</title><link>https://madtea.lol/blog/introducing-madtea/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://madtea.lol/blog/introducing-madtea/</guid><description>&lt;p&gt;Git tooling was designed when the only developer in your terminal was you. Add an AI agent to that terminal, and familiar commands start failing in new ways: &lt;code&gt;git remote -v&lt;/code&gt; leaks a token into the agent&amp;rsquo;s context, a well-meaning issue edit pastes over your bug repro steps, &lt;code&gt;git reset --hard&lt;/code&gt; erases uncommitted work.&lt;/p&gt;
&lt;p&gt;madtea is a Forgejo/Gitea client built for that shared terminal: one binary, two ways in. A &lt;code&gt;gh&lt;/code&gt;-style CLI for you. An MCP server for your agent. Every command is safe to hand to an agent, and every guardrail explains itself to a human.&lt;/p&gt;</description></item></channel></rss>