Inbox & calendar sweeps
Dude checks connected accounts, finds messages and meetings that need attention, and reports back without turning your morning into admin work.
✦ All-in-one operator for modern personal work
Build. Launch. Delegate with Dude.
Dude turns recurring work into supervised workflows across email, calendar, GitHub, research, chat, browser tasks, and scheduled checks.
✓ scoped connectors✓ visible trails✓ approval gates
What Dude can do
Useful help with work you already repeat.
Chat-driven work orders
Send a Telegram instruction, then let Dude search, inspect, summarize, queue a browser task, or come back with a precise approval request.
Recurring operations
Daily briefs, AM research, issue checks, reminders, and system reports run on schedule with logs you can inspect afterward.
Human-controlled actions
Sensitive steps route through review first: sending, posting, buying, deleting, or changing external systems.
How it works
Start with one workflow. Expand after it proves itself.
Bring one live workflow
Pick a task that already repeats: inbox triage, a daily briefing, issue monitoring, or a report that keeps slipping.
Connect the smallest surface
Grant the accounts, files, browser profile, or internal tools that workflow actually needs. Nothing else has to be in scope.
Promote after it proves itself
Run with logs and review. Add automation only when the workflow is boring, reliable, and worth keeping alive.
Private infrastructure
Trust comes from boundaries, logs, and restraint.
Dude is designed for workflows that touch personal accounts, internal tools, and operational context — built around scoped access, review checkpoints, and recoverable state instead of pretending autonomy is always the goal.
Private runtime
Runs on infrastructure you control instead of a generic shared assistant surface.
Scoped connectors
Email, calendar, files, browser, chat, and GitHub are connected per workflow.
Approval gates
External or sensitive actions pause for human confirmation before they leave the machine.
Audit trail
Work leaves a readable trail: tool calls, summaries, failures, recoveries, and follow-up state.
Under the hood
OpenClaw and Hermes power the operator layer.
Runtime, scheduling, memory, tools, and messaging sit under a friendly assistant surface you can actually operate.
1Chat / Telegram intake
Requests, mentions, and status updates
2Scheduler / cron
Reminders, recurring checks, heartbeats
3Tools layer
Browser, files, web, GitHub, calendar
4Memory / state
Daily notes and curated long-term state
5Review / approval
Human control before sensitive operations
start small
Book a 20-minute workflow reviewBring one repetitive workflow.
If it proves useful, promote it. If it does not, keep the blast radius tiny.