[FEATURE] Use ISO-8601/ISO-3339 UTC Timestamp as prefix to export filenames.

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

The issue with the current timestamp prefix on exported context files is that they easily conflict with existing files if you make several exports during a session. I have to default to appending a unique suffix to the timestamp, like 'a' .. 'z'.

2026-01-20a-this-session-is-being-continued-from-a-previous-co.txt

Since the timestamp prefix does not include the time, it is easy to add a suffix to the timestamp that is not in the correct order making it more difficult to quickly find the correct file.

The timestamp prefix on exported files does not indicate a timezone nor the time, so I do not know whether it is UTC or local time.

Since the timestamp prefix does not indicate a timezone, I cannot provide more information as to why timestamp spans two days when multiple exports are performed in a 24 hour period.

=====================

All of these reasons make it difficult to quickly export context multiple times in a session and have the filenames appear in proper order and avoid overwriting existing files within a 1 minute range of a previous one... Same timestamp hence same filename. Using an ISO-8601/3339 UTC timestamp format will provide unique filenames, to 1 second resolution, that are properly ordered when displayed in a file browser. Yes, it is true that I can edit the current timestamp, but this change is so simple and so useful, why not make it?

Proposed Solution

Use an ISO-8601/3339 UTC timestamp format will provide unique filenames, to 1 second resolution, that are properly ordered when displayed in a file browser. Yes, it is true that I can edit the current timestamp, but this change is simple, useful, and an established best practice, so why not make it?

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

File operations

Use Case Example

_No response_

Additional Context

_No response_