<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Desktop AI Agent on ToolGenix — Open-Source AI &amp; Developer Tools: Honest Hands-On Reviews</title><link>https://toolgenix.nxtniche.com/tags/desktop-ai-agent/</link><description>Recent content in Desktop AI Agent on ToolGenix — Open-Source AI &amp; Developer Tools: Honest Hands-On Reviews</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://toolgenix.nxtniche.com/tags/desktop-ai-agent/index.xml" rel="self" type="application/rss+xml"/><item><title>LobsterAI: Desktop AI Agent That Actually Works (Quick Look)</title><link>https://toolgenix.nxtniche.com/posts/lobsterai-desktop-ai-agent-quick-look/</link><pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate><guid>https://toolgenix.nxtniche.com/posts/lobsterai-desktop-ai-agent-quick-look/</guid><description>LobsterAI from NetEase AI is the first open-source desktop AI agent for your files, terminal, and browser. I tested Cowork mode — here&amp;#39;s what happened.</description><content:encoded><![CDATA[<p>I should not be this surprised that an AI agent actually did what I asked.</p>
<p>You know the pattern: upload a CSV to ChatGPT, ask for &ldquo;analyze this,&rdquo; and you get a polite paragraph that says <em>nothing</em>. No charts. No actionable output. Just a summary of what it <em>would</em> do if it had access. LobsterAI — 5,400 stars on GitHub, the first open-source desktop AI agent from NetEase AI&rsquo;s Youdao division — doesn&rsquo;t have that problem. It connects to your real desktop: files, terminal, browser, local projects. And it actually executes.</p>
<h2 id="what-makes-cowork-different">What Makes Cowork Different</h2>
<p>The headline feature here is <strong>Cowork mode</strong>. Instead of generating text about what it would hypothetically do, LobsterAI opens a bridge to your actual working environment. Give it a spreadsheet, and it&rsquo;ll write a Python analysis script, run it locally, and generate a visualization page. Give it a folder of PDFs, and it&rsquo;ll batch-process them into a structured report. And every file-accessing tool call gates behind your approval — I got a permission dialog asking &ldquo;LobsterAI wants to read <code>/Users/me/data/sales.csv</code>&rdquo; before anything touched my disk.</p>
<p>Under the hood, it runs on <strong>OpenClaw</strong> — their custom open-source agent framework that ships with 28+ built-in skills. Web search, docx/xlsx/pptx generation, video creation via Remotion, browser automation via Playwright, image generation via Seedream, stock analysis — the list is long. Plus it supports the MCP protocol, so you can plug in external tools the same way you would with Claude Desktop. So the OpenClaw agent framework is what makes this different from every other &ldquo;AI that browses your files&rdquo; demo. If you&rsquo;re into agent toolkits, I covered a similar ecosystem in the <a href="/posts/composio-quick-review-2026-06-11/">Composio review</a>.</p>
<h2 id="the-phone-command-your-pc-trick">The Phone-Command-Your-PC Trick</h2>
<p>This is the part that made me stop scrolling the README and actually install it. LobsterAI bridges to <strong>7 IM platforms</strong>: WeChat, WeCom, DingTalk, Feishu, QQ, Telegram, and Discord. You send a message from your phone, the desktop agent picks it up, executes, and fires the result back.</p>
<p>So I set up the Telegram bridge. Sent it: &ldquo;Research the global AI Agent market and turn <code>traffic-report.pdf</code> into a PPT deck.&rdquo; And it came back six minutes later with a generated slide deck on my desktop and a summary pushed to my phone. Did it while I was making coffee. That&rsquo;s the kind of &ldquo;AI assistant&rdquo; I signed up for.</p>
<table>
	<thead>
			<tr>
					<th style="text-align: left">Capability</th>
					<th style="text-align: center">LobsterAI (Cowork)</th>
					<th style="text-align: center">Chat-based AI</th>
					<th style="text-align: center">Portal-based Agent</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td style="text-align: left">Desktop access</td>
					<td style="text-align: center">Full (files/terminal/browser)</td>
					<td style="text-align: center">None (sandbox)</td>
					<td style="text-align: center">API-limited</td>
			</tr>
			<tr>
					<td style="text-align: left">Phone remote control</td>
					<td style="text-align: center">✅ 7+ IM platforms</td>
					<td style="text-align: center">❌</td>
					<td style="text-align: center">Partial</td>
			</tr>
			<tr>
					<td style="text-align: left">Tool execution</td>
					<td style="text-align: center">Local (your machine)</td>
					<td style="text-align: center">Cloud sandbox</td>
					<td style="text-align: center">Cloud</td>
			</tr>
			<tr>
					<td style="text-align: left">Open Source</td>
					<td style="text-align: center">✅ MIT</td>
					<td style="text-align: center">❌</td>
					<td style="text-align: center">Varies</td>
			</tr>
			<tr>
					<td style="text-align: left">Permission gating</td>
					<td style="text-align: center">✅ Per-call approval</td>
					<td style="text-align: center">N/A</td>
					<td style="text-align: center">✅</td>
			</tr>
			<tr>
					<td style="text-align: left">Built-in skills</td>
					<td style="text-align: center">28+ (incl. MCP)</td>
					<td style="text-align: center">Plugin-based</td>
					<td style="text-align: center">Limited</td>
			</tr>
	</tbody>
</table>
<h2 id="what-i-actually-ran">What I Actually Ran</h2>
<p>Install flow is straightforward if you&rsquo;re comfortable with <code>npm</code> — clone, <code>npm install</code>, then <code>npm run electron:dev:openclaw</code> for the first launch. But the first build takes a while because it clones and compiles the OpenClaw runtime. On my Ryzen 9 workstation it took about three and a half minutes. After that, subsequent launches via <code>npm run electron:dev</code> are instant — it reuses the cached runtime.</p>
<p>My first task was simple: &ldquo;Analyze the <code>product-growth.xlsx</code> in my Downloads folder and build me a visualization page.&rdquo; Honestly, I didn&rsquo;t expect it to find the right file on the first try. But it did — correctly, not a cached path, not a sandbox — wrote a Python script with matplotlib, generated an HTML dashboard, and opened it in my browser. That&rsquo;s about 12 seconds of actual execution time after the initial agent warmup.</p>
<h2 id="what-to-watch-for">What To Watch For</h2>
<p>Still, it&rsquo;s not a finished product. <strong>835 open issues</strong> on the repo tells you the team is building and shipping fast — but you&rsquo;ll hit rough edges. The Electron app is RAM-hungry (about 400 MB idle). And the Cowork permission dialog appears <em>every single time</em> for file access unless you approve the session — which is good for security but can get annoying during long workflows. Plus some of the IM integrations (WeChat, QQ) require Chinese-platform accounts that your average Western developer won&rsquo;t have. Telegram and Discord work fine though.</p>
<h2 id="bottom-line">Bottom Line</h2>
<p>Yet LobsterAI is the first genuinely desktop-grade open-source AI agent from a major vendor. If you&rsquo;re tired of chat interfaces that promise desktop access and deliver nothing, this is the real thing. Sure, it&rsquo;s rough, it&rsquo;s RAM-heavy, and the first build takes a minute — but the Cowork architecture is right. Your desktop, your tools, your data, actually doing work. For another take on AI agent infrastructure from a Chinese tech giant, check out my <a href="/posts/openviking-context-database-review/">OpenViking review</a>.</p>
]]></content:encoded></item></channel></rss>