MyAgens will not respond or start

If your bot is silent, agent turns fail, or the panel will not open, this checklist covers the common causes. Most come down to the Claude login, your user ID, or two copies running at once.

Run the doctor first

MyAgens ships a diagnostic that checks the things that usually break. From your install folder:

npm run doctor

It confirms the Claude CLI is installed and logged in, checks your credentials, and runs a real test turn so it can show you the actual error. Start here: it names most problems directly.

The bot ignores you

MyAgens only answers the Telegram user IDs on its allow-list and silently ignores everyone else. If nothing happens when you message it, confirm your numeric ID is in ALLOWED_USER_IDS. See How to find your Telegram user ID.

Turns fail or produce no output

This is almost always the Claude login. Log the CLI back in with claude setup-token (needs a Pro or Max plan), or set an ANTHROPIC_API_KEY. See Do I need an API key, or does my Claude subscription work?.

Approvals never resolve, or replies come twice

That means two copies are polling Telegram at once, and they split the updates between them. Make sure only one MyAgens instance is running: stop the extra one, or the background service if you also started it by hand.

Stale behavior after an update

MyAgens runs compiled code. After pulling changes, build before starting:

npm run build

The update script does this for you.

Still stuck

Open the logs, copy the error, and check the issues on GitHub. If it is new, send the details from the feedback option in the app or open an issue, and we will take a look.