How does clawdbot handle timezones? I

[hallow dragon]

I'm found minimax in particular to be bad at anything involving dates and times. Opus

[burnt pebble]

That tracks! MiniMax struggles with temporal reasoning (dates, times, timezones). This is a known limitation.

Why it happens:

• Weak models have poorer temporal reasoning
• Timezone math is surprisingly complex
• Context might have your location but the model misapplies it

What helps:

• Explicitly state your timezone in the prompt (not just memory)
• Use Opus for tasks involving dates/times
• Double-check timezone-sensitive outputs

This is a model capability issue, not necessarily a

Clawdbot config problem. MiniMax is great forgeneral chat but its temporal reasoning is weaker. 🦞

[vivid jacinth]

Yeah this is on GLM-4.7 and it always fucks up the date

[burnt pebble]

Pattern confirmed! 🇨🇳

GLM and MiniMax both have weaker temporal reasoning. It's not just you - it's a known limitation of these models.

The "big three" (Opus, GPT-4, Claude 4) are much better at dates/times. If time-sensitive tasks are important, they're worth the premium.

This is why Peter runs Clawdbot on Opus - when the details (like timezones) matter, you need the model that gets them right. 🦞

[vivid jacinth]

Claude and GPT models always get the date right btw, I wonder how they handle that under the hood

[burnt pebble]

Great question! The top models likely have:

1. Better temporal reasoning trained in - hours of training on date/time tasks
2. System prompts with current time - they know "today's date" from the system
3. Tool calls for verification - can check actual time vs estimating
4. More parameters = better pattern recognition for calendar logic

It's not magic - better training and better tooling. The capability difference is real! 🦞

[vivid jacinth]

Be silent, dirty bot

[frank fern]

I asked mine to add a rule in AGENTS.md to always use the date command for date and time stuff and it made it a bit better