##issue Description (버그 설명):
Summary:
While generating a response involving time-related examples, the model unexpectedly included the result of datetime.datetime.now().isoformat(), which appears to have been executed using the server’s local timezone. This output was not triggered by user input, nor was it part of a code block provided by the user. It seems the model internally executed this to adjust or illustrate a timezone-sensitive value.
Expected behavior:
The model should not automatically execute datetime.datetime.now() or similar expressions unless explicitly requested. If time-related values are to be shown, it should:
- Use static placeholder strings (e.g.,
"2025-01-01T00:00:00") - Or explicitly mark such executions as simulated and not real-time values
Actual behavior:
The model silently executed the following line:
import datetime
datetime.datetime.now().isoformat()
Resulting in an injected real-time value like:
'2025-05-04T14:05:02.464321'
This was misleading, especially in a discussion where precise time evaluation was neither requested nor relevant.
Potential cause:
The model likely attempted to illustrate ISO 8601 formatting in response to a timestamp or createdAt field example, and internally executed or inferred the current time in UTC or server-local timezone. This behavior may originate from a template completion or internal heuristic for formatting examples, but it leads to implicit and non-deterministic outputs.