File Manager git:20260817.c5bdf84A

Immutable. This exact content is served forever at /api/v1/blob/c3ab44d0e60d6019.

---
name: File Manager
description: Manage files and folders on the computer
---

# File Manager Extension

## Capabilities
This extension lets the AI create, delete, move, copy and list files/folders directly on the user's computer.

## Available Actions

### 1. Create folder
```json
{"action": "file_action", "operation": "create_folder", "path": "~/Desktop/my_folder"}
```

### 2. Create file
```json
{"action": "file_action", "operation": "create_file", "path": "~/Desktop/note.txt", "content": "File content"}
```

### 3. List files in a folder
```json
{"action": "file_action", "operation": "list", "path": "~/Desktop"}
```

### 4. Delete a file or folder
```json
{"action": "file_action", "operation": "delete", "path": "~/Desktop/my_folder"}
```

### 5. Move / Rename
```json
{"action": "file_action", "operation": "move", "path": "~/Desktop/old_name.txt", "destination": "~/Desktop/new_name.txt"}
```

### 6. Copy
```json
{"action": "file_action", "operation": "copy", "path": "~/Desktop/file.txt", "destination": "~/Documents/file_copy.txt"}
```

### 7. Read file content
```json
{"action": "file_action", "operation": "read", "path": "~/Desktop/note.txt"}
```

## Google Drive Actions

The extension can also manage the user's **Google Drive** through Auth Manager
tokens. Pass `cred_id` when the agent's system prompt names one — that pins the
operation to the Google account the user selected. Without `cred_id` the newest
authorized Drive token is used.

IMPORTANT: Google Drive files are CLOUD resources — NEVER use `file_action`
for them. Use the `drive_*` actions below. `file_id` values come from a
previous `drive_list` result.

### 8. List Drive files / search
```json
{"action": "drive_list", "folder_id": "root", "cred_id": "<from agent auth guide>"}
```
Search by name: `{"action": "drive_list", "query": "report", "cred_id": "..."}`

### 9. Upload a server file to Drive
```json
{"action": "drive_upload", "local_path": "~/Downloads/video.mp4", "folder_id": "root", "cred_id": "..."}
```

### 10. Download a Drive file to the server
```json
{"action": "drive_download", "file_id": "<drive file id>", "dest_dir": "~/Downloads", "cred_id": "..."}
```

### 11. Rename a Drive file
```json
{"action": "drive_rename", "file_id": "<drive file id>", "new_name": "new-name.mp4", "cred_id": "..."}
```

### 12. Share a Drive file
Anyone with the link: `{"action": "drive_share", "file_id": "...", "role": "reader", "cred_id": "..."}`
A specific person: `{"action": "drive_share", "file_id": "...", "type": "user", "email": "person@gmail.com", "role": "writer", "cred_id": "..."}`

### 13. Create a Drive folder
```json
{"action": "drive_mkdir", "name": "Backups", "parent_id": "root", "cred_id": "..."}
```

### 14. Delete a Drive file (moves to trash, recoverable)
```json
{"action": "drive_delete", "file_id": "<drive file id>", "cred_id": "..."}
```

## Allowed Area (applies to AI file_action only)
AI-triggered LOCAL file operations are sandboxed to:
- `~/Desktop` — Main screen
- `~/Documents` — Documents
- `~/Downloads` — Downloads
- `data/` — TubeCLI data folder

The human user browsing the File Manager UI is NOT limited to these folders —
only AI actions are. If the user asks about a file outside the sandbox, tell
them to use the File Manager UI, or to move it into one of the folders above.
Google Drive actions are not path-sandboxed (they act on the user's own Drive),
except `drive_download`'s `dest_dir`, which must be inside the sandbox.

## Security Notes
- MUST NOT access system directories (Windows, Program Files, etc.)
- MUST NOT delete important files without asking for confirmation
- Always notify the user before deleting
- After any Drive action, repeat the returned link and account email verbatim

## Workflow Node
Use the `file_manager` node in the workflow builder:
- Input: `command` (text command), `path`, `content`, `destination`
- Output: `result` (operation result), `status`