Make datetime info message more explicit to prevent LLM confusion about current year

[tlongwell-block]

Problem

Users are reporting that Goose defaults to thinking it's 2024 even when the info message contains the correct 2025 datetime. This has been observed in version 1.15.0-block.202511212016-e9b9d.

Current Behavior

The current info message format is:

<info-msg>
Datetime: 2025-12-10 19:01:27

</info-msg>

Despite this message being present near the top of the context, the LLM still defaults to 2024 when making queries (e.g., looking at 2024 data instead of 2025 data).

Proposed Solution

Make the datetime message more verbose and explicit, such as:

<info-msg>
It is currently 2025-12-10 19:01:27

</info-msg>

Or even more explicit:

<info-msg>
The current date and time is: 2025-12-10 19:01:27
The current year is: 2025

</info-msg>

This would make it clearer to the LLM what the actual current date/time is, reducing confusion about which year's data to query.

@goose go ahead and get on this. Thanks

Additional Context

• Reported by: @jom in #goose-help
• Version: 1.15.0-block.202511212016-e9b9d
• The issue occurs consistently across multiple chat windows
• Users currently have to explicitly tell Goose "it's currently December 2025" to work around this

cc: @tlongwell-block

[tlongwell-block]

/goose

[tlongwell-block]

/goose solve this minimally. Just have it say "It is currently ${datetime}" inside the info message. This is a one line change. Do not add additional tests. If there is an existing one that the depends on the specific string in the datetime info message, go ahead and update it as needed

[tlongwell-block]

/goose solve this minimally. Just have it say "The current datetime is ${datetime}" inside the info message. This is a one line change. Do not add additional tests. If there is an existing one that the depends on the specific string in the datetime info message, go ahead and update it as needed

[tlongwell-block]

/goose solve this minimally. Just have it say "It is now ${datetime}" inside the info message. This is a one line change. Do not add additional tests. If there is an existing one that the depends on the specific string in the datetime info message, go ahead and update it as needed

[tlongwell-block]

/goose solve this minimally. Just have it say "It is currently ${datetime}" inside the info message. This is a one line change. Do not add additional tests. If there is an existing one that the depends on the specific string in the datetime info message, go ahead and update it as needed

[tlongwell-block]

/goose solve this minimally. Just have it say "It is currently ${datetime}" inside the info message. This is a one line change. Do not add additional tests. If there is an existing one that the depends on the specific string in the datetime info message, go ahead and update it as needed

[tlongwell-block]

/goose solve this minimally. Just have it say "It is currently ${datetime}" inside the info message. This is a one line change. Do not add additional tests. If there is an existing one that the depends on the specific string in the datetime info message, go ahead and update it as needed

[tlongwell-block]

/goose solve this minimally. Just have it say "It is currently ${datetime}" inside the info message. This is a one line change. Do not add additional tests. If there is an existing one that the depends on the specific string in the datetime info message, go ahead and update it as needed