Email automation sub-agent issues
I'm having trouble getting the email-automation agent properly authenticated so it can read my Gmail inbox.
Here's what's happening:
- When I tell the main agent Samwise to spawn the email-automation agent for my Gmail inbox summary, it says:
- I've already:
- Made sure the email-automation agent is correctly configured in my agents folder.
- Verified that the gateway is running and that the gateway token is up to date (via
- Checked that the Discord bot is correctly set up and connected to OpenClaw (using the bot token from Discord Dev Portal).
- However, when I try to spawn the agent (via agents route or subagents), it still fails with an authentication/device token issue.
Could you please help me:
1. Confirm what the correct way is to set up and authenticate the email-automation sub-agent in my current version (OpenClaw 2026.2.15)?
2. Check if I may need to rotate the device token for the agent or gateway, and how to do that safely without breaking anything.
3. Guide me through making sure the email-automation agent has the right gateway and device token settings so it can spawn correctly and actually read Gmail.
4. Point out any common config mismatches between gateway, main agent, and email-automation agent that could cause this error.
Here's what's happening:
- When I tell the main agent Samwise to spawn the email-automation agent for my Gmail inbox summary, it says:
"I'm getting an authentication error when trying to spawn the sub-agent. This error suggests there's an issue with the device token authentication."
- I've already:
- Made sure the email-automation agent is correctly configured in my agents folder.
- Verified that the gateway is running and that the gateway token is up to date (via
openclaw doctor --generate-gateway-tokenopenclaw gateway --force- Checked that the Discord bot is correctly set up and connected to OpenClaw (using the bot token from Discord Dev Portal).
- However, when I try to spawn the agent (via agents route or subagents), it still fails with an authentication/device token issue.
Could you please help me:
1. Confirm what the correct way is to set up and authenticate the email-automation sub-agent in my current version (OpenClaw 2026.2.15)?
2. Check if I may need to rotate the device token for the agent or gateway, and how to do that safely without breaking anything.
3. Guide me through making sure the email-automation agent has the right gateway and device token settings so it can spawn correctly and actually read Gmail.
4. Point out any common config mismatches between gateway, main agent, and email-automation agent that could cause this error.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
