Feature Request
Problem
There's no way to share files or documents between team members through AgentOps. When working on shared research (e.g. domain research, competitive analysis, design docs), there's no mechanism to send artifacts to a colleague or collaborate on shared files.
Currently the only option is to use external tools (email, Slack, Google Drive) which breaks the workflow.
Proposed Solution
1. Shared folder (mini P2P)
A shared folder between team members that syncs files, similar to a lightweight peer-to-peer system:
agentops share <file> --to <user> # Send a file to a team member
agentops share list # List files shared with you
agentops share pull # Download shared files to local
The shared folder could live at ~/.claude/shared/ or a configurable path, with files organized by sender.
2. Document upload to org
agentops upload <file> --tag <tags> # Upload a document to the org
agentops docs list # List org documents
agentops docs pull <name> # Download a shared doc
Use Case
During a domain research session, I generated a CSV with competitive analysis data that I needed to share with a colleague. Had to leave the AgentOps workflow entirely to share via email.
Ideal flow:
agentops share domain-research.csv --to alex
Alex receives it in their shared folder next time they start a session.
Implementation Ideas
- Could use the existing AgentOps API/auth to handle file transfer
- Files could be stored in the org's cloud storage (already exists for skills)
- Size limit (e.g. 10MB) to keep it lightweight
- Optional: integrate with skills so shared research can inform skill execution
Priority
Nice-to-have, but would significantly reduce context-switching when collaborating.
Feature Request
Problem
There's no way to share files or documents between team members through AgentOps. When working on shared research (e.g. domain research, competitive analysis, design docs), there's no mechanism to send artifacts to a colleague or collaborate on shared files.
Currently the only option is to use external tools (email, Slack, Google Drive) which breaks the workflow.
Proposed Solution
1. Shared folder (mini P2P)
A shared folder between team members that syncs files, similar to a lightweight peer-to-peer system:
The shared folder could live at
~/.claude/shared/or a configurable path, with files organized by sender.2. Document upload to org
Use Case
During a domain research session, I generated a CSV with competitive analysis data that I needed to share with a colleague. Had to leave the AgentOps workflow entirely to share via email.
Ideal flow:
Alex receives it in their shared folder next time they start a session.
Implementation Ideas
Priority
Nice-to-have, but would significantly reduce context-switching when collaborating.