Support OpenScience (`@synsci/openscience`) as a client integration
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, typescript
Research direction
Start by reading the existing ocx start auto-injection paths for Codex, Claude Code, and Claude Desktop, along with the ocx doctor checks. Then investigate how OpenScience stores local configuration and exposes providers and models. Done means OpenCodex can configure OpenScience to use the local proxy, show routed models, and include it in doctor checks.
Written by the indexing model from the issue text.
Description
Area
Multiple areas
What are you trying to accomplish?
I want to use OpenScience (synthetic-sciences/openscience, npm: @synsci/openscience) with models routed through OpenCodex (Gemini, Claude, DeepSeek, Kimi, GLM, etc.), with automatic configuration similar to how OpenCodex currently supports Codex, Claude Code, and Claude Desktop.
What prevents this today?
Currently, ocx start and auto-injection support Codex, Claude Code, and Claude Desktop. To use OpenCodex with OpenScience, users must manually configure an OpenAI-compatible custom provider endpoint via openscience local add pointing to http://127.0.0.1:10100/v1.
What should OpenCodex do?
- Detect OpenScience installations or local configuration directory and support automatic proxy injection (or an explicit command such as
ocx inject openscience). - Expose routed models in OpenScience's provider/model selector.
- Include OpenScience in
ocx doctorchecks.
Example usage or interface
ocx start
# OpenCodex detects OpenScience and injects local proxy config:
# [opencodex] OpenScience configured -> http://127.0.0.1:10100/v1
openscience
Alternatives or workarounds
Manually adding a local OpenAI-compatible provider in OpenScience pointing to http://127.0.0.1:10100/v1.
Additional context
- OpenScience repository: https://github.com/synthetic-sciences/openscience
- OpenScience package: https://www.npmjs.com/package/@synsci/openscience
- OpenScience is an open-source AI workbench for scientific research based on the OpenCode architecture.
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.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 667
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lidge-jun/opencodex
-
Transient OAuth login failure persists in getLoginStatus and masks active account in dashboardMay be free again A pull request for this issue was closed without being merged. Openaccount-pool bug gui
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
lidge-jun/opencodex#7378 · 2 comments ·
Maintainers usually reply within 1 day
-
account-pool enhancement needs-design proxy
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lidge-jun/opencodex#6737 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(google-antigravity): discoverAntigravityProject fails with missing_project when project is not auto-discovered, rejecting valid tokensPossibly taken @yobushka claimed this today. Openaccount-pool bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
lidge-jun/opencodex#7382 · 2 comments ·
Maintainers usually reply within 1 day
-
account-pool bug needs-design provider proxy
Difficulty 4/5 3-5 days Newbie friendliness 42/100
lidge-jun/opencodex#7380 · 3 comments ·
Maintainers usually reply within 1 day
-
account-pool bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
lidge-jun/opencodex#7377 · 2 comments ·
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
check:failed streams:edit
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
iptv-org/iptv#55901 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
package:ios ships XCFrameworks with absolute symlinks, which SwiftPM refuses to extractPossibly taken @cusnirvladislav claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/rock#740 ·
-
S: triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
area:workflow bug ready-for-human
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fil-donadoni/tolaria#6108 ·
Maintainers usually reply within 1 day