Logs

No credentials or configuration are written to disk; API to MCP manifests are the one exception, and they never hold a secret. What RavensPort does write lives under %AppData%\RavensPort\ and %LocalAppData%\RavensPort\ on Windows, and under ~/.config/RavensPort/ and ~/.local/share/RavensPort/ on Linux:

Path	Contents
`%AppData%\...\logs\activity-YYYYMMDD.log`	Proxied requests and responses, connects, refreshes, route reloads, vault operations. Rotates every 2 days, auto-deletes after ~10
`%AppData%\...\logs\errors.log`	Unhandled exceptions and provider errors with stack traces
`%LocalAppData%\...\manifests\`	API to MCP manifests, one file per bridge, plus a timestamped copy of each save — see API to MCP
`%LocalAppData%\...\pass-session\`	RavensPort's encrypted Proton Pass session, if you signed in from the app. Unreadable without the session key, which is held by Windows Hello on Windows and by the desktop keyring on Linux, never in this folder
`%LocalAppData%\...\cli\pass-cli\`	A Proton Pass CLI downloaded by a version before 4.3.1. Still used if it is there; nothing writes here any more

On Linux, read %AppData% as ~/.config and %LocalAppData% as ~/.local/share.

The Settings tab can open either log, open the folder, or prune old ones.

Redaction. Activity logs record request paths and query parameter names; values are redacted, and tokens are never logged. Vault operations log the command, exit code, and duration — never the output, which for a read is the item contents. Control characters are escaped so one event can only ever produce one line: request paths reach the log percent-decoded, so without this a caller could write fabricated entries.

Startup warnings. Any stored upstream or token endpoint using plain http off-machine is flagged as STARTUP WARNING. New entries are rejected when added, but the vault can also be edited directly in your password manager, which bypasses that check.

Edit this page on the wiki Request support · Report vulnerabilities privately