trustclaw  by ComposioHQ

Summary

TrustClaw provides a self-hostable personal AI agent with vector memory and extensive tool integrations, designed for secure, automated task execution. It targets users seeking a 24/7 AI assistant that operates autonomously, overcoming the security risks of local AI agent setups through a managed, remote execution environment.

How It Works

Rebuilt for security, TrustClaw uses OAuth for all tool connections and sandboxed remote execution for actions, preventing local credential exposure or code execution. Its long-term memory leverages Postgres with pgvector and a 3-layer context management system. LLM and embedding calls route through Vercel AI Gateway, abstracting direct API key management.

Quick Start & Requirements

Deployment is simplified via the Vercel CLI (npx @composio/trustclaw deploy), with setup estimated around two minutes. Prerequisites include Vercel and GitHub accounts, and a Composio API key. Local development requires Postgres + pgvector. Links to a Vercel Template, Demo Video, and Launch Video are provided.

Highlighted Details

• OAuth Integrations: Connects to 1000+ apps (Gmail, GitHub, Slack) solely via OAuth.
• Zero Setup: Frictionless onboarding; no complex API key configurations needed initially.
• Autopilot Operation: Supports cron-scheduled agent runs for recurring tasks.
• Sandboxed Execution: Actions run in isolated, ephemeral cloud environments for enhanced security.
• Security Model: Prioritizes secure credential management, remote code execution, and audit trails over local agent vulnerabilities.

Maintenance & Community

The README does not specify contributors, sponsorships, or community channels. For security issues, contact sarah@composio.dev.

Licensing & Compatibility

Released under the MIT license, allowing commercial use and closed-source linking. Built on the Composio SDK.

Limitations & Caveats

Vercel Hobby plan limits cron jobs to daily and function durations to 300 seconds. Public deployments require implementing rate limiting and usage caps, as the project lacks built-in billing or throttling to prevent credit drain.