File Sender

Packages workspace files into a ZIP, generates a companion description file, and notifies the Manager to deliver them to the user. Files are persisted locally to .file-outbox/ first — even if notification fails, the files are safe.

All required environment variables are injected automatically by the Manager at instance creation. No manual configuration needed.

Core Workflow

Step 1: Compose a Description

Before running the script, write a concise description of what you generated. This description will be saved as a .txt file alongside the ZIP in .file-outbox/, serving as a human-readable summary for the user.

The description should include:

• - What files/project were generated
• The main purpose of the files
• How to use them (brief instructions)

Good example:
CODEBLOCK0

Bad example:
CODEBLOCK1

Step 2: Package and Send

Pass the source path and the description text to the script:

CODEBLOCK2

The script will:

1. 1. Validate the path — Only allows files under /home/node/workspace/, blocks symlink traversal
2. Create a ZIP — Single file zip, directory zip -r, 500MB limit
3. Write description — Saves the description text as {file_id}.txt in INLINECODE7
4. Persist locally — Both ZIP and TXT are stored in .file-outbox/ (safe on disk)
5. Notify Manager — Sends a lightweight POST with metadata only (no file body)
6. Manager pulls — Manager's background task pulls the ZIP from the Agent and forwards it

Core design: After step 4, files are safely on disk. Steps 5-6 failing does NOT lose the files.
The Manager retries automatically — the user will always receive the files eventually.

Step 3: Confirm the Result

The script outputs the result. Even if notification fails, the files are safely persisted locally. The system will retry delivery automatically.

Quick Examples

CODEBLOCK3

Sending Multiple Non-Adjacent Files

Collect them into a temporary directory first:

CODEBLOCK4

What Gets Saved in .file-outbox/

For each delivery, two files are created:

CODEBLOCK5

The .txt file contains the exact description you provided, serving as a persistent record of what was sent and why.

When to Trigger

Output Examples

Success:
CODEBLOCK6

Notification failure (files still safe):
CODEBLOCK7

Limits

Environment Requirements

• - OPENCLAW_INSTANCE_NAME — Instance name (auto-injected by Manager)
• INLINECODE14 — File Push service URL (auto-injected by Manager)
• INLINECODE15 — Instance-specific push token (auto-injected by Manager)
• INLINECODE16 and zip commands must be available in PATH