[FEATURE] Use actual current date/year in system prompt

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When requesting a search or documentation, Claude currently uses 2024 as the reference year. This may mislead users who expect up-to-date responses. For example, when asking Claude to search for recent documentation or current year information, it defaults to 2024 even though we are now in 2025. This creates confusion and inaccuracy in responses, as users may receive outdated context or miss current developments.

Proposed Solution

Please update the system prompt logic so that Claude uses the actual current system date and year, dynamically, whenever referencing time. This would involve:

1. Modifying the system prompt to include a dynamic date/time variable instead of a hardcoded 2024 reference
2. Automatically updating the current date context when Claude is initialized or starts a conversation
3. Ensuring all time-aware responses reference the correct current year (2025) and date

This will make all responses accurate and context-aware, providing users with up-to-date information that reflects the actual current time period.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

API and model interactions

Use Case Example

User asks: "Can you help me find the latest React documentation?"

Currently: Claude might search for "React 2024 documentation" even though we're in 2025
With the fix: Claude would search for "React 2025 documentation" or "current React documentation"

Another example:
User asks: "What are the current trends in AI development?"

Currently: Claude references 2024 context, potentially missing 2025 developments
With the fix: Claude would know it's 2025 and provide appropriately current information

Additional Context

Technical considerations:

• The system prompt should dynamically inject the current date/time when Claude initializes
• This affects how Claude interprets "current year", "recent", "latest", and other time-relative terms
• This is particularly important for search queries and documentation requests where temporal context matters

This issue may be related to hardcoded dates in the system prompt configuration that need to be updated to use dynamic date injection.