Table of Contents
Keep a session log
Session logs preserve what appeared in the terminal. They are useful for reviewing conversations, bug reports, and trigger matches.
Open Settings → Preferences → Logging.
Readable session logs
Write session logs is enabled by default. Each connection writes a plain-text file under:
Documents/smudgy/<server>/logs/
The filename includes the profile and connection time, for example Gandalf-2026-07-18_19-30-00.log. The file contains processed terminal text, including client echoes and commands you sent. Text removed by a gagging trigger is not present.
Turning logging off closes the current file. Turning it on again starts a new timestamped file.
Raw connection logs
Also write raw connection logs records the bytes received from the server, including ANSI control sequences and telnet protocol data. It takes effect on the next connection and writes a sibling file ending in .raw.log.
Use a raw log when reporting an encoding, color, telnet negotiation, GMCP, MSDP, or compression problem. It is not a more detailed version of the readable log; it is protocol evidence intended for diagnosis.
Review before sharing
Logs can contain private messages, character names, server-sent tokens, and commands. Raw logs may contain data that never appeared visibly. Search and redact the file before attaching it to an issue or sending it to another person.
Auto-login passwords sent through the protected $PASSWORD mechanism are redacted from ordinary command logging, but that safeguard does not make an entire session log safe to publish.
Smudgy's own diagnostic log, Documents/smudgy/smudgy.log, is separate. Include it when the application crashes or reports an internal error, after reviewing it for private paths and server information.