Claw Drive

PassAudited by ClawScan on May 10, 2026.

Overview

Claw Drive appears to be a coherent personal file organizer, with clearly disclosed risks around persistent indexing, optional Google Drive sync, and a background sync service.

Install only if you are comfortable letting an agent organize selected personal files. Before enabling Google Drive sync, review the remote path and .sync-config exclusions, avoid reading/indexing sensitive contents, and remember that the Homebrew-installed binary was not fully present in the reviewed artifacts.

Findings (6)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If you let the agent read a file, details from that file may remain in local logs or the persistent index.

Why it was flagged

The skill explicitly persists extracted file details and searchable descriptions, so sensitive content could remain available in future context/logs if the user allows reading.

Skill content
Extracted content enters the conversation transcript ... logged permanently to `.jsonl` files. ... Descriptions in INDEX.jsonl are also persistent.
Recommendation

Only allow content reading for files you are comfortable indexing, keep descriptions redacted, and use the sensitive/private flow for identity, financial, or confidential documents.

What this means

After sync is enabled, files not excluded by .sync-config can be copied to the configured Google Drive remote.

Why it was flagged

Optional sync sends local drive contents to an external provider through rclone; this is disclosed and purpose-aligned, but it changes the data boundary.

Skill content
fswatch ... rclone sync → Google Drive (cloud backup) ... Files sync within seconds of any change.
Recommendation

Review .sync-config before starting sync, keep sensitive folders excluded, and confirm the Google Drive remote path is a dedicated Claw Drive folder.

What this means

Enabling sync grants rclone access to the chosen Google Drive account/remote.

Why it was flagged

The optional sync setup authorizes a Google Drive rclone remote and stores the resulting token in standard rclone configuration.

Skill content
rclone authorize "drive" ... rclone config create gdrive drive config_is_local=false config_token="$token"
Recommendation

Use a Google account and remote folder you trust for this purpose, and revoke the rclone authorization if you stop using the skill.

NoteHigh Confidence
ASI10: Rogue Agents
What this means

Once started, the sync daemon can keep running and uploading changed files until stopped.

Why it was flagged

The background service is disclosed and user-started, but it is persistent and continues syncing after the initial command.

Skill content
`claw-drive sync start` installs a launchd service (`com.claw-drive.sync`) ... The daemon starts on login and restarts on failure.
Recommendation

Run `claw-drive sync status` to check it and `claw-drive sync stop` when you do not want background syncing.

What this means

This review can assess the included scripts and documentation, but not the exact binary Homebrew will install.

Why it was flagged

The required runtime binary is installed from an external Homebrew tap, while the provided artifact set does not include the installed executable itself.

Skill content
brew | formula: dissaozw/tap/claw-drive | creates binaries: claw-drive
Recommendation

For higher assurance, review the Homebrew formula and installed binary source before installing.

What this means

Incorrect paths or overly broad actions could remove or reorganize files inside the Claw Drive directory.

Why it was flagged

The CLI includes file mutation and deletion capabilities, which are expected for a drive manager but should remain user-directed.

Skill content
`claw-drive delete <path> [--force]` | Delete a file, its index entry, and dedup hash
Recommendation

Use dry-run/review flows where available and confirm paths before force deletion or migration.