permissions. Before connecting a bot to shared channels, check each platform's DM pairing, allowlist and group access policies; the README warns that approving a private sender does not restrict group access everywhere.
Who it is forA user who wants to message their agent from their phone and run cron style automations.
The problemChannels and automations stop when the interactive launcher closes.
The outcomeA background gateway serving chat channels and scheduled automations, with logs you can check.
What you need first
- Python with uv or pip; install with `uv tool install nanobot-ai`
- A model provider configured through the onboarding wizard, or a local LLM
- Optional chat app accounts such as Telegram or Slack for channels
Steps
- Configure a model first with
nanobot onboard --wizard - Ask Nanobot in the WebUI to help connect Telegram and allow only your account, as the README suggests
- Start the gateway with
nanobot gateway --background - Manage it with
nanobot gateway status,nanobot gateway logsandnanobot gateway stop
Prompt for your agent
With HKUDS/nanobot, connect my Telegram account as a channel restricted to my user only, start `nanobot gateway --background`, and show me `nanobot gateway status`.
Caveat. Exact channel settings are in the README's linked chat app guide and channel reference.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for HKUDS/nanobot and "Keep Nanobot running for chat apps and automations"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer