heyagent

HeyAgent CLI connects Claude Code and Codex to Telegram, allowing developers to interact with AI agents through chat messages entirely from their phone or terminal. The tool operates fully locally without external servers or cloud storage, making it suitable for teams prioritizing privacy and control. Users can switch between Claude and Codex providers mid-session, manage multiple sessions, and send text, images, documents, audio, and video attachments through Telegram. Setup uses either QR-code phone pairing or manual bot token entry, storing all configuration locally. The skill supports both Telegram commands and local CLI input, with message queuing and provider execution control through permission flags.

[{"step":1,"action":"Install HeyAgent and connect your preferred notification platform (Slack, Telegram, WhatsApp, or terminal). Use the HeyAgent CLI to authenticate: `heyagent auth --platform [slack|telegram|whatsapp|terminal]`","tip":"For Slack, create a dedicated channel like #agent-alerts and invite HeyAgent as a member."},{"step":2,"action":"Configure monitoring rules for your agents. Use the HeyAgent config file or CLI to specify events to track: `heyagent config --events [task_completed|task_failed|progress_update] --agent [claude|codex]`","tip":"Start with critical events (failures, timeouts) before adding progress updates to avoid notification fatigue."},{"step":3,"action":"Integrate HeyAgent with your existing workflows. For example, link it to your CI/CD pipeline by adding a step in your GitHub Actions workflow: `- name: Monitor Agent - uses: heyagent/action@v1 with: events: task_completed, task_failed`","tip":"Use the `--context` flag to include project names or priority levels in notifications for better filtering."},{"step":4,"action":"Test the setup by triggering a dummy event. Run a test command: `heyagent test --event task_failed --project test-project` and verify the alert appears in your chosen platform.","tip":"Check your notification platform's settings to ensure HeyAgent has permission to send messages."},{"step":5,"action":"Monitor and refine. Review notification logs with `heyagent logs` and adjust rules as needed. For example, mute non-critical events during off-hours using `heyagent config --schedule '0-8'`.","tip":"Use the `--format json` flag to export logs for further analysis in tools like Grafana or ELK."}]