I'm currently getting the following error when sending a message through telegram:
[Telegram] Connected and polling for updates
👋 This is mini-swe-agent version 1.17.3.
Loading global config from '/home/andrew/.config/mini-swe-agent/.env'
(╥_╥) error, retrying...
⚠️ API call failed (attempt 1/6): AuthenticationError
⏱️ Time elapsed before failure: 0.27s
📝 Error: Error code: 401 - {'error': {'message': 'No cookie auth credentials found', 'code': 401}}
It looks like the CLI interface resolves dynamically granted credentials from auth.json and updates the environment variables, but the Gateway interface (hermes-agent running Telegram polling) missed this step and instead relies on static api keys from the .env file or environment. Consequently, mini-swe-agent running via the Telegram adapter wasn't receiving the proper auth tokens, causing the failure during API calls.
I'm currently getting the following error when sending a message through telegram:
[Telegram] Connected and polling for updates
⚠️ API call failed (attempt 1/6): AuthenticationError
👋 This is mini-swe-agent version 1.17.3.
Loading global config from '/home/andrew/.config/mini-swe-agent/.env'
(╥_╥) error, retrying...
⏱️ Time elapsed before failure: 0.27s
📝 Error: Error code: 401 - {'error': {'message': 'No cookie auth credentials found', 'code': 401}}
It looks like the CLI interface resolves dynamically granted credentials from auth.json and updates the environment variables, but the Gateway interface (hermes-agent running Telegram polling) missed this step and instead relies on static api keys from the .env file or environment. Consequently, mini-swe-agent running via the Telegram adapter wasn't receiving the proper auth tokens, causing the failure during API calls.