PortliftGet started
Menu
Browse the guides
PORTLIFT / File Safety

Your files. Your decision.

What Portlift can access, which changes need approval, and exactly what a destination backup can recover.

Local access starts with the companion

The public website serves the interface and stores roadmap votes. Agent file access stays with the installed companion, which runs on 127.0.0.1 with your operating-system account’s file permissions. It can discover supported agent locations and read the agent folders you choose. It is not an operating-system sandbox.

Run portlift ui for a local dashboard. With portlift ui --web, open the printed session link and explicitly connect the hosted dashboard to this machine. Pairing is one-time and expires after five minutes. Relaunch it if the page is refreshed or the connection expires.

Saved versions, receipts, and backups live in the local library. Package Check reads your selected archive in the browser; it does not upload it.

Review the exact changes

The migration preview lists paths, diffs, compatibility notes, and required permissions. Applying uses the prepared plan and checks the current file contents against the preview.

  • Replacement of existing content can require explicit replace approval.
  • Overwriting files edited since a previous Portlift write requires approval.
  • Broader destination permissions and configured commands have separate approvals when required by the plan.

MCP is read-only by default. With writes enabled, each request must be approved in Saved Agents; approvals expire after ten minutes and can be consumed once.

Which files are backed up

Before a migration or sync writes files, Portlift backs up the destination paths marked Create or Update. Existing regular files are stored with their bytes and file mode. For a new file, the backup records that the path did not exist.

This covers the planned changes, not your entire project or computer. Unchanged and skipped paths are not part of that migration backup. Non-regular files and recognized wallet-key material paths are excluded.

Local backups can contain sensitive content.

Backups preserve the original bytes of included files. They are not encrypted by Portlift. Protect the library using your device and backup storage controls.

The separate Back up action captures adapter-recognized native files at the saved agent’s known locations. A saved version is a library snapshot, not a full folder backup.

What restore will do

Restore
Put an existing file back to its saved contents. This can replace later edits; read the diff.
Delete
Remove a file that did not exist before, only when its contents still match Portlift’s recorded write.
Skip
Leave a newly created file in place if it has been edited since the migration.
Unchanged
Leave a file alone when it already matches the backup or was and remains absent.

Before restoring or deleting affected files, Portlift makes a safety backup of their current state. The dashboard rejects a restore if the file state has changed since its preview. Symlink checks apply before restore writes.

Follow the recovery walkthrough →

Inspect packages before trusting them

Exports omit recognized credential values; detection is not a guarantee that arbitrary text contains no secrets. Inspect content before sharing it. Package Check reports integrity, signature information, credential findings, and executable files.

A valid signature verifies the signed content with the included key. It does not by itself establish who you should trust or that the agent’s instructions are safe.

Open Package Check →