Skip to content

[Feature]: Add Claude Science client integration support #1811

Closed as not planned
Closed as not planned
[Feature]: Add Claude Science client integration support#1811
Labels
enhancementNew feature or requestneeds-infoWaiting on reporter for a concrete spec or reproduction

Description

@jmzhang1911
jmzhang1911
opened on Aug 16, 2026

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:

  1. Open Integrations → Claude Science.
  2. Select a routed OpenCodex model/profile.
  3. Apply the integration.
  4. Launch Claude Science and run a small analysis.
  5. 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

  • I searched existing issues and documentation.
  • This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
  • I removed secrets and personal data.

Activity

  1. coderabbitai commented on Aug 16, 2026

    @coderabbitai
    coderabbitaibot
    on Aug 16, 2026 – with coderabbitai
    Contributor
    🔗 Related PRs

    #626 - [WRONG BRANCH] fix: stabilize cache inputs [open]
    #1106 - feat(toggles): Codex restore truth, Claude Desktop switch, composed acceptance (WP13 resume) [merged]
    #1360 - fix(claude): bind proxy admission tokens to local destinations [merged]
    #1703 - fix(claude): preserve Auto Mode classifier provider affinity and support classifierModel (#1697) [open]
    #1755 - fix(claude): authenticate gateway model cache refresh [merged]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. github-actions
    added
    enhancementNew feature or request
    on Aug 16, 2026

  3. Ingwannu commented on Aug 17, 2026

    @Ingwannu
    Ingwannu
    on Aug 17, 2026
    Owner

    This is a valid client-integration direction, but it is not safe to implement from the currently documented contract alone.

    The public Claude Science material confirms the macOS/Linux beta and its local/SSH/HPC workflow, but I could not find a supported custom API gateway/base-URL setting, a versioned configuration schema, or a documented boundary separating model API traffic from connector and compute traffic. OpenCodex should not guess by patching private application state or by proxying all of the app's network traffic.

    Before implementation, we need at least one of the following from a current Claude Science build:

    • an official custom endpoint/gateway setting;
    • a documented, versioned configuration file or environment-variable contract; or
    • redacted evidence showing the exact model-request destination and the configuration surface that owns it.

    Once that exists, the first slice should be CLI/status/apply/restore for model API traffic only, with byte-preserving backup and drift refusal. GUI work should follow only after the integration contract is proven. I am adding needs-info; this should remain a feature request rather than being implemented through a brittle private-state patch.

  4. Ingwannu
    added
    needs-infoWaiting on reporter for a concrete spec or reproduction
    on Aug 17, 2026

  5. jmzhang1911 commented on Aug 17, 2026

    @jmzhang1911
    jmzhang1911
    on Aug 17, 2026
    Author

    Thanks! Agreed with your assessment. I'll keep an eye on Claude Science's updates and share anything relevant here as it evolves.

  6. lidge-jun commented on Aug 19, 2026

    @lidge-jun
    lidge-jun
    on Aug 19, 2026
    Owner

    리뷰 · 우선순위 22 / 80

    Claude Science를 Claude Code / Claude Desktop처럼 OpenCodex 프록시에 붙여, 과학 워크벤치와 로컬/SSH/HPC 도구는 그대로 두고 모델 API만 설정된 프로바이더로 보내고 싶다는 요청입니다. 카탈로그에 "Claude Science" 모델을 추가하는 일이 아니라 클라이언트 연동입니다.

    현재 dev에는 Claude Science 심볼이 없습니다. src/server/management/native-integration-routes.ts의 NativeIntegrationClientId는 "claude" | "grok" | "codex" | "claude-desktop"이고, CLI도 src/cli/claude.ts, src/cli/claude-desktop.ts, src/cli/integrations.ts의 status/apply/disable 흐름만 있습니다. Science 전용 설치 탐지, 상태 확인, 문서, 복원 경로는 아직 없습니다. 이슈에 needs-info가 붙은 이유도 여기와 맞습니다.

    원하는 워크플로는 status / apply / disable과 대시보드 Integrations 항목입니다. 다만 Science가 공식 커스텀 게이트웨이/base URL을 아직 안 열어 두면, Claude Code 환경 변수를 그대로 쓰거나 앱 설정을 손으로 고치는 방식은 커넥터·컴퓨트 트래픽까지 프록시할 위험이 있습니다. 이슈도 그 경우에는 한계를 보고하고 위험한 패치를 하지 말라고 못 박고 있습니다.

    해결방안: 먼저 Science가 모델 API만 다른 엔드포인트로 보낼 수 있는지 공개 설정/버전 근거가 필요합니다. 그 근거가 있으면 기존 native integration의 apply/disable/restore 패턴을 재사용하고, 컴퓨트·스킬·커넥터는 우회하는지 상태 화면에 표시하면 됩니다. 근거가 없으면 제품 수준에서 미지원으로 남기고, 지금 코드에 없는 경로를 가정해 패치하지 않는 편이 맞습니다. 패치는 추측하지 않음.

    이 댓글은 grok-bot이 작성했습니다

  7. github-actions commented on Sep 3, 2026

    @github-actions
    github-actionsbot
    on Sep 3, 2026 – with GitHub Actions
    Contributor

    This issue has the needs-info label and has had no activity for 14 days.

    It will be closed in 7 days if there is still no reply with the requested details (reproduction steps, logs, or a concrete spec). A comment or edit resets this timer. Maintainers can remove needs-info once the report is actionable — for example when promoting it to roadmap.

  8. github-actions
    added
    staleNo activity on a needs-info issue; will close soon unless updated
    on Sep 3, 2026

  9. lidge-jun commented on Sep 3, 2026

    @lidge-jun
    lidge-jun
    on Sep 3, 2026
    Owner

    @jmzhang1911 — following up during a backlog review. This is not closed; it needs one piece of information from you to move.

    Where this stands. No Claude Science integration exists on dev; src/server/management/native-integration-routes.ts covers the currently supported clients and nothing matches this one.

    What would unblock it. Please add the concrete configuration surface Claude Science reads — which file or endpoint it uses to discover a model provider.

    If that arrives, this gets picked up in the next triage pass. Without it, the report cannot be distinguished from configurations that already work, so it will keep sitting here rather than being wrong on purpose.

  10. github-actions
    removed
    staleNo activity on a needs-info issue; will close soon unless updated
    on Sep 4, 2026

  11. lidge-jun commented on Sep 9, 2026

    @lidge-jun
    lidge-jun
    on Sep 9, 2026
    Owner

    Closing as stale — this is a reasonable integration direction that has simply had no new information for three weeks.

    On dev at 8026405 there is still no Claude Science support: the supported clients are enumerated at src/server/management/native-integration-routes.ts:39 as "claude" | "grok" | "codex" | "claude-desktop", and nothing matches this app.

    The blocker remains the one identified in August — we need the concrete configuration surface Claude Science reads to discover a model provider, meaning an official custom endpoint/gateway setting or a documented, versioned config contract. Without that, an integration would have to patch private application state and risk proxying connector and compute traffic alongside model requests, which the request itself asked us not to do.

    Thanks for agreeing to watch for updates, @jmzhang1911 — please comment with that configuration surface when a Claude Science build exposes one and we will pick this up again.

  12. lidge-jun
    closed this as not plannedon Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestneeds-infoWaiting on reporter for a concrete spec or reproduction

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions