Everyone$19 one-timeAuto Mode

Inbox Agent

3 urgent, 5 action needed, 12 FYI, 8 newsletter.

Email categorization, summarization, and digest

$19one-time purchase

$ npx seclaw add inbox-agent --key YOUR_TOKEN

Self-hosted

Docker isolated

Any LLM provider

Your data stays yours

Live Preview

What this looks like in Telegram

You

Check my inbox

seclaw

Inbox Digest URGENT (2) • [CTO] Server down — P0, needs response now • [Client] Contract deadline — signature by EOD ACTION (4) • [PM] Sprint planning — confirm for Wednesday • [HR] Benefits enrollment — deadline Friday FYI (8) · NEWSLETTER (5) Reply with a number for details.

— Inbox Management

Automation Schedule

Every 2 hours

Scan Gmail inbox for new emails

Instant

URGENT emails sent to Telegram immediately

On demand

Full inbox digest on request

How It Works

pipeline

Scan (every 2h) --> Categorize --> Summarize --> Preview (Telegram)
                                              --> [Approve] --> Deliver digest
                                              --> [Reject]  --> Skip

sample output

URGENT (2)
- [CTO] Server down in production -- P0 incident, needs immediate response
- [Client] Contract deadline tomorrow -- Signature required by EOD

ACTION (4)
- [PM] Sprint planning invite -- Wednesday 10am, please confirm
- [HR] Benefits enrollment -- Open until Friday

FYI (8)
- [GitHub] PR #142 merged -- Feature branch cleanup
- [Slack] Channel archive notice -- #old-project archived

NEWSLETTER (5)
- TechCrunch, Morning Brew, TLDR, Hacker Newsletter, Product Hunt

What You Get

4 categories

URGENT / ACTION / FYI / NEWSLETTER

Instant alerts

URGENT emails bypass the digest schedule

Human-in-the-loop

Approve or reject before delivery

Concise

1-2 line summaries per email

Composio OAuth

Secure Gmail connection via OAuth

Why seclaw?

OpenClaw proved the demand — 68K+ GitHub stars. But it ships with zero container isolation: API keys exposed to every MCP container, your home directory mounted to root-privileged processes, port 5678 open with no auth.

Every seclaw template runs in Docker with hard guardrails — no root, no host access, no exposed ports. Security enforced at runtime, not in the system prompt.

Non-root containers

Zero inbound ports

API keys sealed per service

512MB / 1 CPU limits

See the full OpenClaw vs seclaw comparison