File: README.md Copy Chapter

LobsterAI

[Download LobsterAI](https://lobsterai.youdao.com/#/download-list)

LobsterAI is a desktop Agent that can operate in your real working environment: local files, terminal commands, browser workflows, documents, spreadsheets, slides, IM channels, scheduled jobs, and project workspaces.

Cowork is the LobsterAI product/session layer. OpenClaw is the runtime and gateway underneath it. That split lets LobsterAI keep local persistence, permissions, UI state, artifacts, agents, memory, and IM bindings in the desktop app while using OpenClaw for agent execution.

Features Copy Chapter

Desktop Cowork Sessions Copy Section

Run long-form Agent tasks against local projects and files. LobsterAI streams progress, keeps session history, renders tool output, and asks for approval before sensitive actions such as file operations, terminal commands, or network access.

Multi-Agent Workflows Copy Section

Create custom Agents with their own identity, model choice, skills, working directory, enabled state, and IM bindings. Keep the Main Agent for general work and use specialized Agents for repeatable roles.

Expert Kits Copy Section

Install scenario-oriented Expert Kits that package capability selections and references for common workflows. Kits are selected independently from direct skills, so a workflow can combine curated kits with individual tools.

Skills Copy Section

LobsterAI ships with 28 built-in skills configured in SKILLs/skills.config.json, including web search, Word documents, spreadsheets, PowerPoint, PDF processing, Remotion video generation, browser automation, image/video generation, stock research, content writing, email, weather, and skill creation.

MCP Servers Copy Section

Connect external tools and data sources through Model Context Protocol servers. LobsterAI stores user-configured servers locally and syncs enabled servers into OpenClaw.

Scheduled Tasks Copy Section

Create recurring work either by conversation or through the scheduled task UI. Use it for daily news digests, inbox summaries, website monitoring, weekly reports, and other repeatable work.

IM Remote Control Copy Section

Reach your desktop Agent from WeChat, WeCom, DingTalk, Feishu/Lark, QQ, Telegram, Discord, NetEase IM, NetEase Bee, POPO, and email. Multi-instance platforms can bind different accounts or channels to different Agents.

Rich Artifacts Copy Section

Preview and manage generated HTML, SVG, images, video, Mermaid diagrams, code, Markdown, text, documents, and local service artifacts inside the desktop app.

Local Memory And Data Copy Section

Sessions and app data live locally in SQLite. OpenClaw workspace memory uses files such as MEMORY.md, USER.md, SOUL.md, and daily notes, so durable preferences and project context can carry across sessions.

Real-World Prompts Copy Chapter

How It Works Copy Chapter

• Renderer: React, Redux Toolkit, Tailwind, artifact renderers, settings, agent/session UI, skills, MCP, scheduled tasks, and IM configuration.
• Main process: Electron lifecycle, IPC, SQLite persistence, auth, logging, OpenClaw startup, runtime repair, skill sync, IM gateways, and artifact services.
• OpenClaw integration: openclawEngineManager, openclawConfigSync, openclawRuntimeAdapter, and coworkEngineRouter translate LobsterAI state into OpenClaw runtime behavior.

Install Copy Chapter

Desktop Copy Section

Download the latest macOS and Windows installers from Official Website or GitHub Releases.

Run From Source Copy Section

Requirements:

• Node.js >=24.15.0 <25
• npm

git clone https://github.com/netease-youdao/LobsterAI.git
cd LobsterAI
npm install

First development run:

npm run electron:dev:openclaw

Daily development after the pinned OpenClaw runtime exists:

npm run electron:dev

The renderer dev server runs at http://localhost:5175.

Developing Copy Chapter

# Production renderer bundle
npm run build

# Electron main/preload TypeScript build
npm run compile:electron

# Official Vitest entry used by CI
npm test

# Full ESLint across src; may expose existing legacy debt
npm run lint

# CI-style lint for touched TypeScript files
npx eslint --ext ts,tsx --report-unused-disable-directives --max-warnings 0 <files>

OpenClaw Runtime Copy Section

The pinned OpenClaw version and third-party plugin list live in package.json under openclaw.

# Build the current-platform runtime manually
npm run openclaw:runtime:host

# Use a custom OpenClaw source checkout
OPENCLAW_SRC=/path/to/openclaw npm run electron:dev:openclaw

# Force runtime rebuild
OPENCLAW_FORCE_BUILD=1 npm run electron:dev:openclaw

# Keep a local OpenClaw checkout on its current branch/tag
OPENCLAW_SKIP_ENSURE=1 npm run electron:dev:openclaw

Packaging Copy Chapter

Build desktop installers

# macOS
npm run dist:mac
npm run dist:mac:x64
npm run dist:mac:arm64
npm run dist:mac:universal

# Windows
npm run dist:win

# Linux
npm run dist:linux

Packaging bundles the OpenClaw runtime under Resources/cfmind. Windows builds also bundle a portable Python runtime under resources/python-win, so end users do not need to install Python manually.

Offline or private-source packaging can use:

• LOBSTERAI_PORTABLE_PYTHON_ARCHIVE
• LOBSTERAI_PORTABLE_PYTHON_URL
• LOBSTERAI_WINDOWS_EMBED_PYTHON_VERSION
• LOBSTERAI_WINDOWS_EMBED_PYTHON_URL
• LOBSTERAI_WINDOWS_GET_PIP_URL

Project Map Copy Chapter

Security And Data Copy Chapter

• Renderer windows use context isolation, disabled Node integration, and sandboxing.
• Renderer-to-main access goes through preload IPC APIs.
• Sensitive tool actions are permission-gated and logged.
• App data is stored locally in lobsterai.sqlite under Electron userData.
• OpenClaw state, workspace memory, generated config, and gateway logs live under userData/openclaw.

Community & Support Copy Chapter

Join the WeChat group for help, feedback, and release updates:

Please use the repository issue templates for bugs and feature requests. For pull requests, include a short summary, linked issue when relevant, screenshots for UI changes, and notes for Electron-specific behavior such as IPC, storage, runtime, or windowing changes.

Star History Copy Chapter

License Copy Chapter

MIT License

Built and maintained by NetEase Youdao.

File: SKILLs/imap-smtp-email/README.md Copy Chapter

IMAP/SMTP Email Skill

Read and send email via IMAP/SMTP protocol. Works with any IMAP/SMTP server including Gmail, Outlook, 163.com, vip.163.com, 126.com, vip.126.com, 188.com, and vip.188.com.

Quick Setup Copy Chapter

1. Configure accounts in LobsterAI Settings > Email.

LobsterAI writes accounts.json for multi-account setups. Existing .env files are still read as a legacy single-account fallback.

Optional legacy .env format:

# IMAP Configuration (receiving email)
IMAP_HOST=imap.gmail.com
IMAP_PORT=993
[email protected]
IMAP_PASS=your_app_password
IMAP_TLS=true
IMAP_MAILBOX=INBOX

# SMTP Configuration (sending email)
SMTP_HOST=smtp.gmail.com
SMTP_PORT=587
SMTP_SECURE=false
[email protected]
SMTP_PASS=your_app_password
[email protected]

2. Install dependencies:

npm install

3. Test the connection:

node scripts/imap.js check
node scripts/smtp.js test

Account Selection Copy Chapter

# Use the default enabled account
node scripts/imap.js check

# List account IDs without secrets
node scripts/imap.js accounts
node scripts/smtp.js accounts

# Use a specific account
node scripts/imap.js check --account work

# Fan out to every enabled account for read/list commands
node scripts/imap.js check --all-accounts
node scripts/imap.js search --all-accounts --unseen
node scripts/imap.js list-mailboxes --all-accounts

IMAP Commands (Receiving Email) Copy Chapter

Check for new emails Copy Section

node scripts/imap.js check --limit 10
node scripts/imap.js check --account work --limit 10
node scripts/imap.js check --all-accounts --limit 10
node scripts/imap.js check --recent 2h        # Last 2 hours
node scripts/imap.js check --recent 30m       # Last 30 minutes

Fetch specific email Copy Section

node scripts/imap.js fetch 
node scripts/imap.js fetch  --account work

Search emails Copy Section

node scripts/imap.js search --unseen
node scripts/imap.js search --all-accounts --unseen
node scripts/imap.js search --from "[email protected]"
node scripts/imap.js search --subject "important"
node scripts/imap.js search --recent 24h

Mark as read/unread Copy Section

node scripts/imap.js mark-read 
node scripts/imap.js mark-unread  --account work

List mailboxes Copy Section

node scripts/imap.js list-mailboxes
node scripts/imap.js list-mailboxes --all-accounts

SMTP Commands (Sending Email) Copy Chapter

Test SMTP connection Copy Section

node scripts/smtp.js test
node scripts/smtp.js test --account work

Send email Copy Section

# Simple text email
node scripts/smtp.js send --to [email protected] --subject "Hello" --body "World" --confirmed

# HTML email
node scripts/smtp.js send --to [email protected] --subject "Newsletter" --html --body "<h1>Welcome</h1>" --confirmed

# Email with attachment
node scripts/smtp.js send --to [email protected] --subject "Report" --body "Please find attached" --attach report.pdf --confirmed

# Multiple recipients
node scripts/smtp.js send --account work --to "[email protected],[email protected]" --cc "[email protected]" --subject "Update" --body "Team update" --confirmed

Sending is blocked unless --confirmed is passed after the user confirms recipient, subject, sender account, and body.

Common Email Servers Copy Chapter

Important for 163.com:

• Use authorization code (授权码), not account password
• Enable IMAP/SMTP in web settings first

Configuration Options Copy Chapter

IMAP:

• IMAP_HOST - Server hostname
• IMAP_PORT - Server port
• IMAP_USER - Your email address
• IMAP_PASS - Your password or app-specific password
• IMAP_TLS - Use TLS (true for SSL, false for STARTTLS)
• IMAP_REJECT_UNAUTHORIZED - Accept self-signed certs
• IMAP_MAILBOX - Default mailbox (INBOX)

SMTP:

• SMTP_HOST - Server hostname
• SMTP_PORT - Server port (587 for STARTTLS, 465 for SSL)
• SMTP_SECURE - true for SSL (465), false for STARTTLS (587)
• SMTP_USER - Your email address
• SMTP_PASS - Your password or app-specific password
• SMTP_FROM - Default sender email (optional)
• SMTP_REJECT_UNAUTHORIZED - Accept self-signed certs
• EMAIL_REQUIRE_SEND_CONFIRMATION - Set to false only for trusted automation that may send without --confirmed

Troubleshooting Copy Chapter

Connection errors:

• Verify IMAP/SMTP server is running and accessible
• Check host/port settings in .env

Authentication failed:

• For Gmail: Use App Password (not account password if 2FA enabled)
• For 163.com: Use authorization code (授权码), not account password

TLS/SSL errors:

• For self-signed certs: Set IMAP_REJECT_UNAUTHORIZED=false or SMTP_REJECT_UNAUTHORIZED=false

Files Copy Chapter

• SKILL.md - Skill documentation
• accounts.json - Multi-account credentials managed by LobsterAI Settings
• scripts/imap.js - IMAP CLI tool
• scripts/smtp.js - SMTP CLI tool
• package.json - Node.js dependencies
• .env - Legacy single-account credentials fallback

File: SKILLs/web-search/README.md Copy Chapter

Web Search Skill

Real-time web search capability for LobsterAI using Playwright-controlled browser automation.

Overview Copy Chapter

The Web Search Skill enables LobsterAI to perform live web searches using Google and Bing, with automatic fallback when one provider is unavailable. The skill uses Playwright to control a local Chrome browser instance, making all operations transparent and observable.

Features Copy Chapter

• ✅ Real-time Search - Access current web information via Google with Bing fallback
• ✅ Transparent Operations - Visible browser window shows all actions
• ✅ Playwright-Powered - Robust browser automation using playwright-core
• ✅ Simple CLI - Easy-to-use command-line interface for Claude
• ✅ HTTP API - RESTful Bridge Server for advanced integrations
• ✅ Auto-Managed - Electron automatically starts/stops the service
• ✅ Connection Caching - Reuses browser connections for performance
• ✅ Localhost Only - Secure by design, no external exposure

Architecture Copy Chapter

Claude → Bash Tool → CLI Scripts → Bridge Server (localhost:8923) → Playwright → CDP → Chrome

Components:

1. Bridge Server - Express HTTP API for browser control
2. Playwright Manager - Connection and session management
3. Browser Launcher - Chrome lifecycle management
4. Search Engines - Google primary and Bing fallback
5. CLI Scripts - Simplified command-line interface
6. Electron Integration - Automatic service management

Quick Start Copy Chapter

1. Install Dependencies Copy Section

cd SKILLs/web-search
npm install

2. Build Copy Section

npm run build

3. Start Server Copy Section

bash scripts/start-server.sh

4. Perform Search Copy Section

bash scripts/search.sh "TypeScript tutorial" 5

5. Stop Server Copy Section

bash scripts/stop-server.sh

Usage Copy Chapter

Simple Search Copy Section

bash SKILLs/web-search/scripts/search.sh "search query" [max_results]

Examples:

# Search for React 19 features (default 10 results)
bash scripts/search.sh "React 19 new features"

# Search for TypeScript tutorials (limit to 5 results)
bash scripts/search.sh "TypeScript tutorial" 5

# Search for current news
bash scripts/search.sh "AI news 2026" 10

API Usage Copy Section

See examples/basic-search.md for complete API documentation.

Health Check:

curl http://127.0.0.1:8923/api/health

Search:

curl -X POST http://127.0.0.1:8923/api/search \
  -H "Content-Type: application/json" \
  -d '{"connectionId": "...", "query": "...", "maxResults": 5}'

Configuration Copy Chapter

Default configuration in server/config.ts:

{
  browser: {
    cdpPort: 9222,
    headless: false,  // Always visible
    chromeFlags: [/* ... */]
  },
  server: {
    port: 8923,
    host: '127.0.0.1'  // Localhost only
  },
  search: {
    defaultEngine: 'auto',
    fallbackOrder: ['google', 'bing'],
    defaultMaxResults: 10,
    searchTimeout: 30000,
    navigationTimeout: 15000
  }
}

How Claude Uses This Skill Copy Chapter

When Claude needs real-time information, it will:

1. Recognize the need - Questions about current events, latest docs, etc.
2. Check server - Verify Bridge Server is running
3. Execute search - Run bash scripts/search.sh "query" N
4. Parse results - Extract relevant information from Markdown output
5. Answer user - Provide response based on search results

Example Interaction:

User: What are the new features in Next.js 14?

Claude: [Calls: bash SKILLs/web-search/scripts/search.sh "Next.js 14 features" 5]

        Based on the latest search results, Next.js 14 introduces:
        1. Turbopack - 5000x faster than Webpack
        2. Server Actions (stable) - Simplified data mutations
        3. Partial Prerendering - Faster page loads
        ...

API Endpoints Copy Chapter

Browser Management Copy Section

• POST /api/browser/launch - Launch Chrome
• POST /api/browser/connect - Connect to browser
• POST /api/browser/disconnect - Disconnect
• GET /api/browser/status - Get status

Search Operations Copy Section

• POST /api/search - Execute search
• POST /api/search/content - Get URL content

Page Operations Copy Section

• POST /api/page/navigate - Navigate to URL
• POST /api/page/screenshot - Take screenshot
• POST /api/page/content - Get HTML content
• POST /api/page/text - Get text content

Utility Copy Section

• GET /api/health - Health check
• GET /api/connections - List connections

Project Structure Copy Chapter

SKILLs/web-search/
├── README.md                    # This file
├── SKILL.md                     # Skill documentation (for Claude)
├── LICENSE.txt                  # MIT License
├── package.json                 # Dependencies
├── tsconfig.json                # TypeScript config
├── server/                      # Bridge Server source
│   ├── index.ts                 # Express server
│   ├── config.ts                # Configuration
│   ├── playwright/
│   │   ├── manager.ts           # Playwright connection manager
│   │   ├── browser.ts           # Browser lifecycle
│   │   └── operations.ts        # Page operations
│   └── search/
│       ├── types.ts             # Type definitions
│       ├── google.ts            # Google search engine
│       └── bing.ts              # Bing fallback engine
├── scripts/                     # CLI tools
│   ├── start-server.sh          # Start Bridge Server
│   ├── stop-server.sh           # Stop Bridge Server
│   ├── search.sh                # Search CLI
│   ├── test-basic.js            # Basic functionality test
│   └── test-search.js           # Integration test
├── examples/                    # Usage examples
│   └── basic-search.md          # Complete usage guide
└── dist/                        # Compiled output (auto-generated)

Testing Copy Chapter

Basic Functionality Test Copy Section

node scripts/test-basic.js

Tests:

• Browser launch and connection
• Playwright connection management
• Page navigation
• Title and content extraction
• Screenshot capture
• Resource cleanup

Search Integration Test Copy Section

node scripts/test-search.js

Tests:

• Bridge Server startup
• Browser launch via API
• Playwright connection
• Bing search execution
• Result parsing
• Screenshot and text extraction
• Full cleanup

Troubleshooting Copy Chapter

Server Won't Start Copy Section

# Check logs
cat .server.log

# Check if port is in use
lsof -i :8923

# Rebuild
npm run build

Chrome Not Found Copy Section

Install Chrome:

• macOS: https://www.google.com/chrome/
• Linux: sudo apt install chromium-browser
• Windows: https://www.google.com/chrome/

Connection Issues Copy Section

# Clean up
bash scripts/stop-server.sh
rm .connection .server.pid

# Restart
bash scripts/start-server.sh

Security Copy Chapter

• Localhost only - Server binds to 127.0.0.1
• No external access - Not exposed to network
• Isolated profile - Separate Chrome user-data-dir
• Visible operations - All actions shown in browser window
• No credentials - No sensitive operations performed

Performance Copy Chapter

• Server startup: < 2 seconds
• Browser launch: < 3 seconds
• Search latency: < 1 second (network dependent)
• Connection reuse: Cached for multiple searches
• Memory usage: ~80MB (Bridge Server) + Chrome

Requirements Copy Chapter

• Node.js 18+
• Google Chrome or Chromium
• macOS, Windows, or Linux
• Internet connection for searches

Dependencies Copy Chapter

• express - HTTP server
• playwright-core - Browser automation
• uuid - Connection ID generation

License Copy Chapter

MIT License - See LICENSE.txt

Future Enhancements Copy Chapter

Phase 2 (Optional) Copy Section

• Advanced search options (date range, language, region)
• Result caching
• Deep content extraction

Phase 3 (Optional) Copy Section

• Native Cowork tool integration
• Form filling and multi-step automation
• CAPTCHA handling
• Network interception with Playwright

Contributing Copy Chapter

This skill is part of the LobsterAI project. For issues or suggestions:

1. Check existing issues
2. Create detailed bug reports
3. Include logs from .server.log
4. Test with latest version

Credits Copy Chapter

Built with:

• Playwright - Browser automation
• Express - HTTP server
• Chrome DevTools Protocol - Browser control

Support Copy Chapter

For help:

1. Read examples/basic-search.md
2. Check troubleshooting section
3. Review .server.log for errors
4. Test with node scripts/test-basic.js