← all repositories
ComposioHQ/secure-openclaw

Claude in your group chats, with a bouncer at the door

A Node.js gateway that drops a tool-wielding Claude instance into your WhatsApp, Telegram, Signal, or iMessage threads, complete with persistent memory and bouncers for uninvited guests.

1.2k stars JavaScript Agents
secure-openclaw
Not currently ranked — collecting fresh signals.
star history

What it does Secure OpenClaw is a Node.js gateway that bridges Claude (or the open-source Opencode stack) to your personal messaging threads on WhatsApp, Telegram, Signal, and iMessage. It gives the agent read/write access to files, bash execution, and integrations with over 500 third-party apps via Composio, all while storing long-term memories in local Markdown files. You chat with it as you would a contact; it responds and asks for permission before running tools.

The interesting bit The security model is chat-native: instead of API keys guarding endpoints, unrecognized senders are silently dropped and every dangerous tool requires an explicit “Y” reply mid-conversation. It is essentially polite glue code—treating your messaging app as a shell, complete with a two-minute timeout on sudo requests.

Key highlights

  • Supports four messaging platforms (WhatsApp, Telegram, Signal, iMessage) with per-platform allowlists for DMs and groups.
  • Tool approvals are conversation-native: the assistant pauses and asks for a yes/no reply before executing Bash, Edit, or other configured tools.
  • Persistent memory lives in ~/secure-openclaw/ as Markdown files (daily logs, topic notes, and a master MEMORY.md), loaded at the start of each conversation.
  • Scheduled reminders and cron jobs persist in JSON and execute while the gateway is running.
  • Swappable AI backends: Claude Agent SDK or Opencode, switchable via config.

Caveats

  • iMessage is macOS-only and requires a third-party imsg CLI; Signal needs signal-cli registered separately.
  • Memory is strictly reactive: the assistant only writes to its diary when explicitly asked, so it will not proactively log every insight.
  • Tool approvals time out after two minutes, which may stall long-running asynchronous workflows.

Verdict Ideal if you already live in messaging apps and want Claude acting as a persistent, multi-tool assistant without opening a browser. Skip it if you need a managed SaaS with proactive memory and zero CLI dependencies.

Frequently asked

What is ComposioHQ/secure-openclaw?
A Node.js gateway that drops a tool-wielding Claude instance into your WhatsApp, Telegram, Signal, or iMessage threads, complete with persistent memory and bouncers for uninvited guests.
Is secure-openclaw open source?
Yes — ComposioHQ/secure-openclaw is open source, released under the MIT license.
What language is secure-openclaw written in?
ComposioHQ/secure-openclaw is primarily written in JavaScript.
How popular is secure-openclaw?
ComposioHQ/secure-openclaw has 1.2k stars on GitHub.
Where can I find secure-openclaw?
ComposioHQ/secure-openclaw is on GitHub at https://github.com/ComposioHQ/secure-openclaw.

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.