You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
save notices to .thirdshift sub dir (contents of emails) #754
Category: enhancement Summary: Keep each Run notification's text beside its Command log, whether or not it is emailed
Current behavior:
thirdshift builds a Run notification's subject and body only to send them through Resend, when the email flag or the User config asks for one. Nothing keeps the text. Without email, there is no record of what the notification would have said. With email, the only record is the inbox.
Desired behavior:
When a Command that sends Run notifications ends, thirdshift writes the notification's subject and body to a file beside that Command's log, named like it (for example <Command log stem>.notification.txt). It does this whether or not an email is sent, and the text is exactly what was or would have been sent.
Commands that send no notification write no file: a skipped Pass, a Ticket's Run, and a Base fix. The last two are reported in their owning Command's notification. Failing to write the file is a warning and never changes the outcome.
Key interfaces:
The Run notification (RunNotification) and where it builds its subject and body.
The Command log's location and file stem.
The Console's log inventory and thirdshift logs, which must keep working with the new file beside the logs.
Acceptance criteria:
With email off, a finished Run leaves a notification file beside its Command log, holding the subject and body that would have been sent.
With email on (a fake Resend), the file's text equals what was sent.
A Pickup run that dispatched a Run writes one file, beside the Pickup run's Command log. A Spec run writes one, not one per Ticket.
A skipped Pass writes none.
An unwritable log folder produces a warning and the same outcome.
The guide's section on logs names the file.
Out of scope:
Showing notifications in the Console, and retention or cleanup of old files.
Activity
JacobStephens2 commentedon Oct 21, 2026
Agent Brief
Category: enhancement
Summary: Keep each Run notification's text beside its Command log, whether or not it is emailed
Current behavior:
thirdshift builds a Run notification's subject and body only to send them through Resend, when the email flag or the User config asks for one. Nothing keeps the text. Without email, there is no record of what the notification would have said. With email, the only record is the inbox.
Desired behavior:
When a Command that sends Run notifications ends, thirdshift writes the notification's subject and body to a file beside that Command's log, named like it (for example
<Command log stem>.notification.txt). It does this whether or not an email is sent, and the text is exactly what was or would have been sent.Commands that send no notification write no file: a skipped Pass, a Ticket's Run, and a Base fix. The last two are reported in their owning Command's notification. Failing to write the file is a warning and never changes the outcome.
Key interfaces:
RunNotification) and where it builds its subject and body.thirdshift logs, which must keep working with the new file beside the logs.Acceptance criteria:
Out of scope:
Warn when a Session trace cannot be finished