DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to message your project assistant from Telegram or WhatsApp with Spynel

Reach the same Spynel assistant from Telegram or WhatsApp when you are away from the terminal.

Credentials. Connecting Telegram or WhatsApp means linking a messaging account to a local tool, so protect any tokens or account access you set up.

Who it is forA builder who starts work at a desk but wants to check on or direct agents from a phone while away.

The problemAgent work stalls when you are away from the terminal, and checking progress means returning to your computer.

The outcomeA Telegram or WhatsApp channel connected to your running Spynel assistant, so you can send instructions and get replies from your phone.

What you need first

  • macOS or Linux for the curl install, or Node.js 18+ for the npm install
  • An existing coding harness such as Codex or Claude Code, since Spynel uses them to do the work
  • A project directory to run Spynel from

Steps

  1. Start Spynel from your project directory with spynel.
  2. Run /config and set up the Telegram or WhatsApp integration.
  3. Read docs/integrations.md for the setup details for your chosen channel.
  4. Send a test message from Telegram or WhatsApp to the assistant.
  5. Confirm the reply comes back and that the work matches what the terminal shows.

Prompt for your agent

Using the spynel repo at agent0ai/spynel, follow docs/integrations.md to connect <Telegram or WhatsApp> to a Spynel instance running in <project-directory>. Expected output: a test message sent from the phone gets a reply from the same assistant. Verify that the reply matches the state shown in the terminal chat.

Caveat. Telegram and WhatsApp setup details live in docs/integrations.md, and this summary does not describe their exact steps, so follow that doc for them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page