Message Claude from Discord or Telegram While It Works on Your Machine
Claude Code channels let you push messages into a running session from outside your terminal. Set up a Discord or Telegram bot once, and you can check in on long-running tasks or give new instructions from your phone while Claude works on your local files.
Install the Discord plugin, then restart Claude with the channel flag:
# Install once
/plugin install discord@claude-plugins-official
# Start a session with Discord channel active
claude --channels plugin:discord@claude-plugins-official
The first time you DM your bot on Discord, it replies with a pairing code. Paste it in Claude Code to link your account:
/discord:access pair <code>
/discord:access policy allowlist
The same pattern works for Telegram:
claude --channels plugin:telegram@claude-plugins-official
/telegram:access pair <code>
/telegram:access policy allowlist
Once paired, messages you send to the bot arrive in your terminal session as <channel source="discord"> events, and Claude's replies go back to you in the chat.
Security is built in: only sender IDs you've explicitly paired can push messages. Everyone else is silently dropped. The channel only activates when you pass --channels at startup, so it never runs passively in the background.
If Claude hits a permission prompt while you're away, the session pauses. For unattended use, combine channels with --dangerously-skip-permissions in a trusted isolated environment.
Channels turn any chat app into a remote control for Claude Code running on your machine.
via Claude Code Docs — Push events into a running session with channels
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.