anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Support for private storage backends (S3/Object Storage) for the /share command #4746

New Issue
Closed
opened 2026-02-16 17:45:14 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:45:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @TommyHwang on GitHub (Jan 11, 2026).

Originally assigned to: @thdxr on GitHub.

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.

Originally created by @TommyHwang on GitHub (Jan 11, 2026). Originally assigned to: @thdxr on GitHub. 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.
yindo closed this issue 2026-02-16 17:45:14 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4746
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?