Deep sea exploration: #openclaw - 2. A Lobstrosity
After 10 hours of fighting with every part of the OpenClaw 2026.2.15 version I was able to get it running with some custom JSON wizardry only to learn the following:
1. None of the free APIs in OpenRouter actually work. They all say API calls are used upstream and to try again later.
2. Even completely configured correctly, double and triple checked, the telegram token mismatch was impossible to get around. Even creating new bots through the Bot_Father and using different accounts was useless. So I communicated only in terminal.
3. I was able to hatch my new Claw and used /gemini-2.0-flash-lite-001 for the brain. I ran a total of 6 commands including:
* Hello - it said hello back
* [Pairing Code] it said there was a token mismatch even though the only way to get the pairing code is for OpenClaw to send it from your terminal to telegram
* How do we fix this? It said it needed access to the web, which it already had and is configured correctly.
* You have access - three sentences explaining it didn't
* Here is the new token and ID- there is a token mismatch ( I had already updated both correctly, so that wasn't the actual case)
* Your API limit has been reached -try again later
4. I checked my open router balance to see those 6 commands had cost me $.30
So. Since that model of Gemini is $.075 per million in and $.10 per million out. OpenClaw had managed to burn through 4 million tokens in it's 12 minute lifecycle.
How was this possible? It would appear the culprit is HEARTBEAT.md
It seems that 2026.2.15 hits the the API with the entirety of your chat history and it's entire build config every 5 seconds from what I can see.
Action taken. Uninstalled and reverting to... Oh wait? It could not be uninstalled. Funny that. Reverted to a snapshot in Virtual Box from pre install and am installing 2026.1.39 to test with that.
Under sea adventure. Thank fuck I didn't use another API and went with the cheapest option. Some of them are $35 per 2m tokens lol.
Will update soon.
7
npub1zw…ne0qt
2026-02-17 13:17:29 UTC
Author Public Key
npub1zweqn0t62sl5x2a6d289caj383v4c85tysd0f7j0w8s8y65z6chq4ne0qtSeen on
wss://nos.lolPublished at
2026-02-17 13:17:29 UTCEvent JSON
{
"id": "f2587f54f918fb79817ba3c728c1652f6d0ace1a7914400aeb50e3b89899fc5e",
"pubkey": "13b209bd7a543f432bba6a8e5c76513c595c1e8b241af4fa4f71e0726a82d62e",
"created_at": 1771334249,
"kind": 1,
"tags": [
[
"t",
"openclaw"
]
],
"content": "Deep sea exploration: #openclaw - 2. A Lobstrosity\n\nAfter 10 hours of fighting with every part of the OpenClaw 2026.2.15 version I was able to get it running with some custom JSON wizardry only to learn the following:\n\n1. None of the free APIs in OpenRouter actually work. They all say API calls are used upstream and to try again later.\n\n2. Even completely configured correctly, double and triple checked, the telegram token mismatch was impossible to get around. Even creating new bots through the Bot_Father and using different accounts was useless. So I communicated only in terminal.\n\n3. I was able to hatch my new Claw and used /gemini-2.0-flash-lite-001 for the brain. I ran a total of 6 commands including:\n* Hello - it said hello back\n* [Pairing Code] it said there was a token mismatch even though the only way to get the pairing code is for OpenClaw to send it from your terminal to telegram\n* How do we fix this? It said it needed access to the web, which it already had and is configured correctly.\n* You have access - three sentences explaining it didn't\n* Here is the new token and ID- there is a token mismatch ( I had already updated both correctly, so that wasn't the actual case)\n* Your API limit has been reached -try again later\n4. I checked my open router balance to see those 6 commands had cost me $.30\n\nSo. Since that model of Gemini is $.075 per million in and $.10 per million out. OpenClaw had managed to burn through 4 million tokens in it's 12 minute lifecycle.\n\nHow was this possible? It would appear the culprit is HEARTBEAT.md\n\nIt seems that 2026.2.15 hits the the API with the entirety of your chat history and it's entire build config every 5 seconds from what I can see.\n\nAction taken. Uninstalled and reverting to... Oh wait? It could not be uninstalled. Funny that. Reverted to a snapshot in Virtual Box from pre install and am installing 2026.1.39 to test with that.\n\nUnder sea adventure. Thank fuck I didn't use another API and went with the cheapest option. Some of them are $35 per 2m tokens lol.\n\nWill update soon. \n\n",
"sig": "2af869d48e25bc3b02374ff7cc7b3eba2f3d74ead616152bf0bd213bfb386395222556a824200fd0a92535983bc6675cb5d773d684f72d635a04a6fdacc4e320"
}