Hello. Thank you always for your great work.
Currently, the /share feature in OpenCode is a great tool for collaboration, but it seems to store session data on public servers (opencode.ai). In an enterprise environment, this poses a significant security risk as internal code and context could be exposed to the public.
To use this feature within a company, we need the ability to point the share destination to a private infrastructure.
Suggestions I would like to inquire about the following:
Existing Options: Are there any hidden configuration options or environment variables to change the storage backend for /share (e.g., to a private S3 bucket or internal object storage)?
Roadmap: Is there a plan to support custom storage backends or self-hosting the "share" infrastructure in the near future?
Contribution: If there are no immediate plans, I would like to explore the possibility of implementing this feature and submitting a PR. Would the maintainers be open to a proposal that abstracts the storage layer to allow for private S3/Object Storage providers?
Additional Context Many corporate users are restricted from using cloud-based sharing for security compliance. Providing a way to keep data within the company's VPC while still enjoying the collaboration benefits of /share would be a huge improvement for enterprise adoption.
Hello. Thank you always for your great work.
Currently, the /share feature in OpenCode is a great tool for collaboration, but it seems to store session data on public servers (opencode.ai). In an enterprise environment, this poses a significant security risk as internal code and context could be exposed to the public.
To use this feature within a company, we need the ability to point the share destination to a private infrastructure.
Suggestions I would like to inquire about the following:
Existing Options: Are there any hidden configuration options or environment variables to change the storage backend for /share (e.g., to a private S3 bucket or internal object storage)?
Roadmap: Is there a plan to support custom storage backends or self-hosting the "share" infrastructure in the near future?
Contribution: If there are no immediate plans, I would like to explore the possibility of implementing this feature and submitting a PR. Would the maintainers be open to a proposal that abstracts the storage layer to allow for private S3/Object Storage providers?
Additional Context Many corporate users are restricted from using cloud-based sharing for security compliance. Providing a way to keep data within the company's VPC while still enjoying the collaboration benefits of /share would be a huge improvement for enterprise adoption.