Area
Multiple areas
What are you trying to accomplish?
I want to use Claude Science with OpenCodex in the same way that Claude Code and Claude Desktop can use the proxy: keep Claude Science's scientific workbench, local/SSH/HPC compute, skills, connectors, and auditable artifacts while routing supported model requests through providers and models configured in OpenCodex.
What prevents this today?
OpenCodex currently documents and exposes dedicated integrations for Claude Code and Claude Desktop, but not Claude Science. There is no supported setup, status check, or documentation showing whether Claude Science can be pointed at the OpenCodex Anthropic-compatible endpoint without breaking its product-specific workflows.
Because Claude Science is a separate beta app, manually reusing Claude Code environment variables or editing application state is uncertain and fragile. Users cannot tell which requests can safely be proxied, which authentication mode is required, or whether non-model traffic used by scientific connectors and compute orchestration must bypass the proxy.
What should OpenCodex do?
Provide a supported Claude Science integration on macOS and Linux.
The observable workflow should:
- detect or clearly document the supported Claude Science installation/configuration;
- configure only its model API traffic to use the local OpenCodex endpoint;
- support selecting routed models/providers through the existing OpenCodex configuration where Claude Science permits it;
- preserve Claude Science features such as local and remote compute, skills, connectors, specialist/reviewer agents, and reproducible artifacts;
- expose a status/diagnostic view that confirms whether Claude Science is routed or using its native connection;
- restore the previous configuration when the integration is disabled;
- document authentication, limitations, and any Claude Science beta/version compatibility requirements.
If Claude Science does not currently expose a supported custom gateway/base-URL mechanism, OpenCodex should detect that and report the limitation rather than applying an unsafe or brittle patch.
Example usage or interface
One possible CLI workflow (exact command names are only illustrative):
ocx integration claude-science status
ocx integration claude-science apply
ocx integration claude-science disable
Equivalent dashboard workflow:
- Open Integrations → Claude Science.
- Select a routed OpenCodex model/profile.
- Apply the integration.
- Launch Claude Science and run a small analysis.
- Confirm in OpenCodex diagnostics that model calls use the selected route while local scientific tools and compute continue to work normally.
Alternatives or workarounds
Possible workarounds are manually setting Claude Code-style environment variables or editing Claude Science's application configuration. These are undocumented for Claude Science, may be overwritten by app updates, and could accidentally proxy unrelated connector or compute traffic.
Using Claude Code through OpenCodex remains an option, but it does not provide Claude Science's integrated scientific artifacts, curated scientific skills/connectors, native scientific visualization, and reviewer-agent workflow.
Additional context
Anthropic announced Claude Science on June 30, 2026 as a beta AI workbench for scientists on macOS and Linux:
https://www.anthropic.com/news/claude-science-ai-workbench
The announcement describes local, SSH, and HPC operation; more than 60 curated scientific skills/connectors; specialist and reviewer agents; and reproducible artifacts. Claude Science is an app/workbench rather than a new model, so this request is specifically for client integration and safe request routing, not a catalog entry named "Claude Science."
Checks
Area
Multiple areas
What are you trying to accomplish?
I want to use Claude Science with OpenCodex in the same way that Claude Code and Claude Desktop can use the proxy: keep Claude Science's scientific workbench, local/SSH/HPC compute, skills, connectors, and auditable artifacts while routing supported model requests through providers and models configured in OpenCodex.
What prevents this today?
OpenCodex currently documents and exposes dedicated integrations for Claude Code and Claude Desktop, but not Claude Science. There is no supported setup, status check, or documentation showing whether Claude Science can be pointed at the OpenCodex Anthropic-compatible endpoint without breaking its product-specific workflows.
Because Claude Science is a separate beta app, manually reusing Claude Code environment variables or editing application state is uncertain and fragile. Users cannot tell which requests can safely be proxied, which authentication mode is required, or whether non-model traffic used by scientific connectors and compute orchestration must bypass the proxy.
What should OpenCodex do?
Provide a supported Claude Science integration on macOS and Linux.
The observable workflow should:
If Claude Science does not currently expose a supported custom gateway/base-URL mechanism, OpenCodex should detect that and report the limitation rather than applying an unsafe or brittle patch.
Example usage or interface
One possible CLI workflow (exact command names are only illustrative):
Equivalent dashboard workflow:
Alternatives or workarounds
Possible workarounds are manually setting Claude Code-style environment variables or editing Claude Science's application configuration. These are undocumented for Claude Science, may be overwritten by app updates, and could accidentally proxy unrelated connector or compute traffic.
Using Claude Code through OpenCodex remains an option, but it does not provide Claude Science's integrated scientific artifacts, curated scientific skills/connectors, native scientific visualization, and reviewer-agent workflow.
Additional context
Anthropic announced Claude Science on June 30, 2026 as a beta AI workbench for scientists on macOS and Linux:
https://www.anthropic.com/news/claude-science-ai-workbench
The announcement describes local, SSH, and HPC operation; more than 60 curated scientific skills/connectors; specialist and reviewer agents; and reproducible artifacts. Claude Science is an app/workbench rather than a new model, so this request is specifically for client integration and safe request routing, not a catalog entry named "Claude Science."
Checks