OpenClaw Early User Reports Telegram Issues, Agent Profile Hardcoding, and Session Reset Problems

A developer shared their initial experience with OpenClaw after getting it running locally via Docker. They conducted micro tests to understand features and token consumption, connecting Telegram as their first communication channel and linking the Wacli skill for WhatsApp using two phone numbers, plus setting up an initial heartbeat.

Key Observations from Testing

The user noted that many initial orientation problems aren't discussed by content creators who focus on simplicity. Their specific findings include:

• Telegram Blackout Response: Responses on Telegram randomly disappear and reappear, suggesting communication issues between Telegram and OpenClaw, possibly due to wake-up delays.
• Agent Profile Hardcoded: The agent profile was set to "messaging" and couldn't be changed through normal editing. The user discovered it's hardcoded in the source code and manually changed it to "full" for testing.
• Session Reset Issues: When resetting or starting a new session, the agent loses access to Wacli even though it remains active and authenticated. A workaround prompt is needed to restore access, indicating Wacli falls out of the agent's path after reset.

The user concluded that testing and breaking things reveals OpenClaw's nature as a solid foundation for building agents on top. They requested community input on similar issues and solutions, plus recommendations for initial setup and memory management, noting their setup appears to be missing something.