Vault and logging
Every session is written to ~/SerialApp/Vault/ as ordinary files on your
machine. There is no account, no cloud storage, and nothing to sync.
How recording works
Recording starts when you open a port. You do not turn it on.
- Opening a port creates a folder under
Auto Log/, named after the port and the time. - Data is written there as it arrives.
- Clicking Save in the recording bar lets you name the session and moves it into your vault.
- Sessions you never save stay in
Auto Log/.
This means a session you did not expect to care about is still recoverable afterwards.
What is in a session folder
| File | Contents |
|---|---|
log.jsonl |
One JSON object per event: timestamp, data, hex, and direction. |
notes.md |
The notes attached to the session, if any. |
comments.json |
Inline comments pinned to specific lines, if any. |
Because these are plain files, you can move, copy, back up, or read them with other tools.
Organising sessions
The vault sidebar (the Vault icon in the left rail) shows your saved sessions as a tree.
- Drag a session to move it into a folder
- Double-click to rename
- Right-click for the rest
Reopening a session
Click a saved session in the sidebar to open it. It loads as a read-only historical tab. Search, hex, and the decoders all work on it, exactly as they do on a live session.
Revealing the files
Right-click a session and choose Reveal in Finder to open its folder directly.
Exporting
Right-click a session and choose Export Log….
| Format | Result |
|---|---|
.txt |
A readable transcript. |
.csv |
One row per event, for a spreadsheet. |
Notes can be written inline or as a separate notes.md alongside the export.
Inline comments are carried along either way.