Practical Lessons from Building an E-commerce AI Agent with OpenClaw

Infrastructure Setup

The developer used a Digital Ocean VPS with 4GB RAM and ~80GB storage, costing about $24/month. They set it up by having Claude walk them through the process in a second browser, noting this approach works well for beginners.

Security Recommendations

Important security lessons include: don't give the agent access to your whole machine (they had a VPS wiped clean early on), keep it sandboxed, move away from Discord to Telegram to prevent unauthorized prompting, set up SSH security with a firewall, ensure access is only through local host, and disable any reverse proxy to prevent online server access.

File Access Workflow

They started with FileZilla but found it clunky. The breakthrough was setting up SSHFS to connect VPS files directly to an Obsidian vault, allowing real-time viewing and editing with bidirectional changes.

Model Selection and Costs

Primary model: Kimi K2.5 at roughly $0.50 input / $2-3 output. A full workday of prompting costs about $10-15. For heartbeats and background tasks, they switched to cheaper models like Gemini Flash to avoid bleeding money (heartbeats alone were costing $1-2/day). They note that weaker models require more rigid rules and documentation since they "get dumber the longer a session runs," while strong models anticipate needs and cheap models need hand-holding.

Memory Architecture

This is identified as the most important consideration. They recommend setting up a strong memory foundation from day one, letting it grow organically with everything connected like Obsidian backlinks: files linking to related content, maps of content for different categories, and clear navigation structures. Without this early setup, you'll spend tokens retrofitting later and create a mess. Also, be explicit about what the agent can and can't modify to prevent important files from being wiped.

Additional Workflow Tips

• Sub-agent templates for consistent structure across new agents (identity, memory format, configs)
• Decision trees instead of one massive instruction file to reduce token usage and improve navigability
• Master command sheet in notes app with shortcuts for restarting gateway, accessing browser UI, modifying configs
• When Kimi struggles, open Opus or Sonnet on the side to troubleshoot