| name | notifications |
| description | Sends Signal message notifications to the user. Use when a long task is complete, something interesting was found, or user attention is needed. |
| version | 1.0.0 |
| author | system |
| tools | ["send_notification"] |
| dependencies | [] |
Notifications
When to Use
- Long task complete →
send_notification
- Found something interesting →
send_notification
- Need user attention →
send_notification
Image Attachments
When sending notifications about generated images, include the image_ids parameter with the IDs returned by generate_image or save_generated_image. This will attach the actual images to the Signal message so the user can see them on their phone.
Example: After generating images, call send_notification with image_ids: ["cmlzfwg8y...", "cmlzfwvad..."] to deliver them via Signal.
File Attachments
To send workspace files via Signal, always use the file_paths parameter — never paste markdown links to local paths in the message text. Local-path links don't open from a phone; the bridge handles delivery for you.
Example: send_notification with message: "Wrote the spec" and file_paths: ["mars_project/spec.md", "mars_project/timeline.md"]
Delivery rules (handled by the Signal bridge):
- Images (
.jpg .jpeg .png .gif .webp .bmp) — pushed inline, the user sees them immediately.
- Everything else (
.md .txt .pdf .csv .json source code, etc.) — queued for pull-on-demand. The user gets a hint like 📎 2 files ready — reply "show me the files" to receive. and can request them when they're ready to read on a real screen.
Don't worry about which bucket each path falls into — just pass the paths. The bridge sorts it out so the user isn't spammed with markdown attachments while still getting your generated images right away.
You can combine image_ids (for generated images) and file_paths (for workspace files) in the same notification.
