Use iMessage as a Claude Code Channel with the Official Plugin
Claude Code has a plugin system that lets you extend it with new capabilities in a single command. The official iMessage plugin makes it possible to interact with Claude directly through your Mac's Messages app.
/plugin install imessage@claude-plugins-official
Once installed, you can send messages to Claude from iMessage without touching your terminal. It is a full Claude Code channel, not a watered-down chatbot wrapper.
Plugins are fetched from anthropics/claude-plugins-official, Anthropic's managed directory of verified, high-quality Claude Code plugins. The @claude-plugins-official scoping ensures you are always pulling from the official source.
The same pattern works for any plugin in the directory: /plugin install <name>@claude-plugins-official. Visit the GitHub repo to browse everything that is available.
This is handy when you are away from your keyboard but want to fire off a quick task, check on something Claude is working on, or simply prefer texting over typing in a terminal.
If you have a Mac and use iMessage, you now have a Claude Code channel in your pocket.
via @trq212
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.