Daily work journal
When a busy day spans several hosts, transfers and management consoles, the daily work journal helps you retrace your work. Open that day’s file to review your activity and prepare a handover or daily report.
Enable the journal
- Open Tools → Options → Daily work journal.
- Enable Save my daily activity to local files.
- Choose an absolute folder path, or use Browse….
- Save. SuperCharged checks that the folder is writable; recording starts immediately, including for existing sessions.
The journal is off by default. Disable it in Options to stop recording; existing files remain available.
What is recorded
| Activity | Recorded detail |
|---|---|
| UI | Button and menu actions, pointer interactions, selection changes and windows opening or closing. Text-field contents are not recorded by UI tracking. |
| SSH | Sent terminal input and received output, with host, port and username. Records contain readable UTF-8 text and base64 bytes for exact reconstruction, including terminal control sequences. Input may span multiple records. |
| SFTP | Connection, folder browsing, upload, download, remote copy, rename, creation, deletion, metadata and permissions operations. Each operation has paths, a correlation identifier and completion or failure status. File contents are not copied into the journal. |
| Web | Navigation results and page URLs exposed by the integrated IPMI/Proxmox browser, including its in-app window fallback. Browser-internal actions and same-document history depend on what the browser reports. External browser history is unavailable. |
| Sessions | Session audit events, including opening connections and idle lock. |
Daily files
Files are named supercharged-work-YYYY-MM-DD.jsonl, using the computer’s local calendar date. Each line is one JSON event with a timestamp, application session identifier, event kind and details. You can open the file in a text editor or process it with JSON tools. Existing daily files are appended to after a restart; the next event after midnight goes to the next day’s file.
There is no automatic deletion or retention limit. You control archiving and deletion. A write error appears in the application’s messages; sessions and transfers continue, and later events retry writing. Events that could not be written are not recovered automatically.
Sensitive information
SSH input/output and web URLs can contain passwords, tokens, personal data or other sensitive information. The journal is a local plaintext record, separate from the connection audit that excludes passwords. Choose a protected folder and consider who can read it before enabling recording. No journal upload is performed by SuperCharged.

