feat(github): Add configurable share domain and path environment variables #8643

Open
opened 2026-02-16 18:10:29 -05:00 by yindo · 2 comments
Owner

Originally created by @JuanVqz on GitHub (Feb 5, 2026).

Originally assigned to: @thdxr on GitHub.

The GitHub Action currently generates share links with hardcoded URLs (https://opencode.ai/s/{shareId}). This is blocking deployments that need to use different domains (e.g., opncd.ai) or different URL paths (e.g., /share/ instead of /s/).

Add two optional inputs:

  • share_domain: Configure the domain (defaults to opencode.ai)
  • share_path: Configure the path segment (defaults to s)

This allows users to customize share URLs for their deployment environment.

Originally created by @JuanVqz on GitHub (Feb 5, 2026). Originally assigned to: @thdxr on GitHub. The GitHub Action currently generates share links with hardcoded URLs (`https://opencode.ai/s/{shareId}`). This is blocking deployments that need to use different domains (e.g., `opncd.ai`) or different URL paths (e.g., `/share/` instead of `/s/`). Add two optional inputs: - `share_domain`: Configure the domain (defaults to `opencode.ai`) - `share_path`: Configure the path segment (defaults to `s`) This allows users to customize share URLs for their deployment environment.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 5, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #9209: GitHub Action share link uses legacy domain/path

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 5, 2026): This issue might be a duplicate of existing issues. Please check: - #9209: GitHub Action share link uses legacy domain/path Feel free to ignore if none of these address your specific case.
Author
Owner

@JuanVqz commented on GitHub (Feb 5, 2026):

You’re right — this issue https://github.com/anomalyco/opencode/issues/9209 is closely related.

That said, I’m not treating this as a legacy domain problem, but rather as an opportunity to support custom domain configuration in the GitHub Action.

If opncd.ai is deprecated or changed in the future, we’d otherwise need to ship new changes just to update the domain. Instead, allowing users to provide their own configuration gives us more flexibility.

We can keep the current (legacy) domain as the default for now, and potentially add a deprecation warning later — eventually making opncd.ai the default if desired.

Let me know what you think, or if you’d like me to adjust anything. 🙏

@JuanVqz commented on GitHub (Feb 5, 2026): You’re right — this issue https://github.com/anomalyco/opencode/issues/9209 is closely related. That said, I’m not treating this as a `legacy domain` problem, but rather as an opportunity to `support` custom domain configuration in the GitHub Action. If `opncd.ai` is deprecated or changed in the future, we’d otherwise need to ship new changes just to update the domain. Instead, allowing users to provide their own configuration gives us more flexibility. We can keep the `current (legacy) domain` as the default for now, and potentially add a deprecation warning later — eventually making `opncd.ai` the default if desired. Let me know what you think, or if you’d like me to adjust anything. 🙏
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8643