Feature: Direct messaging between team members with attachments

[maxmealing]

Feature Request

Problem

There's no way to communicate with teammates through AgentOps. When you need to send someone a quick note -- "here's the domain research, let me know your top 3" -- you have to leave the workflow entirely and switch to email/Slack.

This is especially painful when Claude Code generates an artifact (CSV, report, analysis) that you want to hand off to a colleague with context.

Proposed Solution

agentops msg <user> "message"                        # Send a text message
agentops msg <user> "message" --attach <file>         # Send with attachment
agentops msg list                                     # Show inbox
agentops msg read                                     # Read unread messages
agentops msg read <id>                                # Read specific message

Example Flow

Sender (max):

agentops msg alex "Domain research is done -- 12 clean names survived. CSV attached. Pick your top 3?" --attach domain-research.csv
# => Sent to alex@bonnard.ai (1 attachment, 4.2KB)

Receiver (alex), next time they start a session or run any command:

📬 1 new message from max@bonnard.ai (2 min ago)
   "Domain research is done -- 12 clean names survived..."
   Run: agentops msg read 1

Reading:

agentops msg read 1
# => From: max@bonnard.ai
# => Date: 2026-04-08 09:15
# => Domain research is done -- 12 clean names survived. CSV attached. Pick your top 3?
# => Attachment: domain-research.csv (4.2KB)
# => Saved to: ~/.claude/shared/inbox/domain-research.csv

Integration with Claude Code

Messages could appear as system reminders when starting a session, so Claude has context:

You have 1 unread message from max:
"Domain research is done -- 12 clean names survived. Pick your top 3?"
Attachment: domain-research.csv

This means Alex's Claude session immediately knows about the research and can help him review it.

Design Considerations

• Lightweight: This is not Slack. Short messages + optional file attachment. No threads, no reactions, no channels.
• Async: Messages queue and deliver on next CLI interaction. No real-time requirement.
• File size limit: 10MB per attachment. Keep it for documents, not media.
• Storage: Messages could use the same backend as skill sync. Files stored in org cloud storage.
• Privacy: Messages are between two users, not broadcast. Only sender and recipient can read.
• Notification: Show unread count on any agentops command. Optional: webhook to email/Slack for notification.

Relationship to Other Issues

• Builds on Feature: Shared folder and document sharing between team members #1 (shared folder) -- attachments use the same file-sharing infrastructure
• Requires Feature: Team directory - list org members and roles #2 (team directory) -- need to know valid recipients

Priority

High -- this is the most natural collaboration primitive. Share a file, add context, get a response. Everything else (shared folders, team directory) supports this.