Fix-datetime-format

[Helmi]

Context

The datetime format for <environment_details> was weird and had the potential to confuse LLMs.

For example it used an international date format that was not defined and fell back to local. In my case (German) todays date output was 6.4.2025 which got confused by LLM for June 4th multiple times (instead of April 6th).

The forced time format of 12h which is completely not used in germany probably added to that confusion.

Implementation

I changed the output to output both, Zulu Time in a standard ISO Timestamp format as well as a local Time string containing the local time including offset as well as the Time Zone name.

Current Zulu Date/Time

2025-04-07T13:56:53.293Z

Current Local Date/Time

Mon Apr 07 2025 15:56:53 GMT+0200 (Mitteleuropäische Sommerzeit)

Get in Touch

@Helmi on Discord

---

Important

Fix datetime format in Cline.ts to include Zulu and local time with timezone details, updating tests accordingly.

• Behavior:
  • getEnvironmentDetails in Cline.ts now outputs both Zulu Time and local time with timezone details.
• Tests:
  • Updated getEnvironmentDetails test in Cline.test.ts to verify new datetime format output.
  • Mocked Date.prototype.getTimezoneOffset to simulate timezone in tests.

^{This description was created by for 027fdf9bf54f3e52772215896d5c3179695de949. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 276c75e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[daniel-lxs]

Thanks for your contribution. We apologize for letting your PR go so long without a review.

We've now shifted to a clearer issue-first workflow to avoid this kind of situation going forward. Please create an issue first if you'd like to revisit this again.

We truly appreciate your patience and would be happy to have you continue contributing.