xtherk

Open Claude Code — AI skill for Claude Code

AI community intermediate

English · 中文 open-claude-code is reconstructed from sourcemap information related to @anthropic-ai/claude-code@2.1.88. Based on t.

How to install Open Claude Code

This entry records only its repository, not the path inside it, so there is no exact command to give. Open xtherk/open-claude-code and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Open Claude Code does

English · 中文 open-claude-code is reconstructed from sourcemap information related to @anthropic-ai/claude-code@2.1.88. Based on t.

Alternatives in AI

CLI 代理 API — English 中文一个为 CLI 提供 OpenAI/Gemini/Claude/Codex 兼容 API 接口的代理服务器 19k ★
Claude AI MCP — Report issues related to MCP integration with Claude here 453 ★
onWatch — Open-source Go CLI that tracks AI API quota usage across 7 providers (Synthetic, Z.ai, Anthropic, Codex, GitHu 397 ★

README

open-claude-code

English · 中文

`open-claude-code` is reconstructed from sourcemap information related to `@anthropic-ai/claude-code@2.1.88`. Based on that recovery work, this repository includes build fixes, structural restoration, and runtime adjustments. Current status: the project has been repaired and can be run locally for code reading and study.

**The recovery, build repair, and documentation work in this repository are driven by Codex.**

Future Direction

This repository is not intended to replace the official release. It exists as a relatively complete local project for source reading, engineering analysis, build process research, and reference on terminal agent implementations.

Project Overview

This repository mainly preserves the core engineering structure of the Claude Code terminal tool, including but not limited to:

src/: restored source code
src/entrypoints/: CLI entrypoints and related initialization logic
vendor/: platform-specific binaries or runtime dependencies
stubs/: local stub dependencies
images/: demo screenshots

Private MCP/NAPI compatibility and related status

The items below describe the current state of the private MCP and related native / NAPI compatibility layers in this recovered build. The table keeps only two signals: **whether the implementation is aligned with the official/original path**, and **the current recovery level (fully complete / mostly complete / graceful-degradation only)**.

Component	Progress (official alignment)	Availability (recovery level)
`@ant/claude-for-chrome-mcp`	Aligned with the official JS / bridge structure.	Mostly complete; still requires the external Chrome extension and socket bridge runtime.
`@ant/computer-use-mcp`	Aligned with the official MCP server / tool schema.	Mostly complete; real execution still depends on the native input / swift backends.
`@ant/computer-use-input`	Aligned with the official `.node` prebuild path.	Mostly complete; the restored path is currently centered on macOS.
`@ant/computer-use-swift`	Aligned with the official `computer_use.node` path.	Mostly complete; the restored native flow is currently centered on macOS.
`image-processor-napi`	Aligned with the official `.node` path, with an added JS fallback.	Mostly complete; native-first, with `sharp` as fallback.
`color-diff-napi`	Self-implemented TypeScript compatibility layer.	Mostly complete; the main path works, but it is not the official native implementation.
`audio-capture-napi`	Aligned with the official `.node` path.	Mostly complete; multi-platform native modules are restored, but real-device validation is still needed.
`url-handler-napi`	Aligned with the official `.node` path.	Mostly complete; the restored native listener is currently macOS-focused.
`modifiers-napi`	Aligned with the official Bun FFI approa