Claude Code Source Recovery (v2.1.88)

This repository is a reconstruction of the @anthropic-ai/claude-code v2.1.88 source code, recovered from source maps. The project follows a modular architecture organized under the src/ directory:

• src/entrypoints/: Contains CLI entry points and initialization logic.
• src/commands/: The command system, including commands like login, mcp, review, and tasks.
• src/components/: Terminal UI components built using React + Ink.
• src/services/: Core business logic, including strategies, synchronization, and remote capabilities.
• src/hooks/: State management for interactive terminal sessions.
• src/utils/: Utility functions for authentication, file operations, and process management.
• src/ink/: Custom infrastructure for terminal rendering.

The recovered source code reveals several key architectural patterns used in the Claude Code CLI:

• Command Loading Mechanism: A hybrid system that supports built-in commands, dynamic skills, plugins, and MCP (Model Context Protocol) commands.
• Terminal UI: Uses React components to construct complex, interactive interfaces within the terminal.
• MCP Integration: Deep implementation and application of the Model Context Protocol within the CLI.
• Feature Flags: Extensive use of feature flags for feature trimming and build-time control logic.

Since this is a source recovery project and not a pre-built package, you cannot run it immediately. To attempt to make the code functional, you must follow these steps:

1. Add a package.json and configure the necessary dependencies.
2. Implement/complete the build toolchain.
3. Handle bun:bundle macros and feature flags.
4. Verify the execution of core commands.

Because version 2.1.88 of @anthropic-ai/claude-code was removed from the official npm registry, a standard npm install will fail. You can install this specific version using the Tencent Cloud mirror cache by pointing directly to the .tgz file.

Note: This installation method relies on the availability of the mirror cache and may not be permanent.

npm install -g https://mirrors.cloud.tencent.com/npm/@anthropic-ai/claude-code/-/claude-code-2.1.88.tgz

The plugin discovery interface is composed of several key UI elements:

• SearchBox: Used for entering queries to find plugins.
• Plugin Details View: Displays information about a selected plugin, including its name, marketplace name, version, and description.
• Plugin Options Flow: A specialized view for handling plugin installation or project-based installation (e.g., install-user or install-project).
• Plugin List: A scrollable list of available plugins.
• Warning Banner: Displays warnings if there are errors during the plugin loading process.

When performing a manual OAuth authentication flow (e.g., when the browser-based flow fails or a prompt appears), the system expects a specific input format. The user must provide the full authorization code string, which includes the authorization code and the state, separated by a hash symbol (#).

Expected Format: authorizationCode#state

If the input does not contain both parts, the authentication will fail with an 'Invalid code' error.

To use XAA (SEP-990) for an MCP server, you must first run claude mcp xaa setup. When adding the server, include the --xaa flag. This mode requires both --client-id and --client-secret (or the MCP_CLIENT_SECRET environment variable) to be provided for the MCP server's Authorization Server (AS).

Note: XAA is only supported for http and sse transports; it will be ignored for stdio servers.

Claude Code uses a diagnostic process to determine how it was installed, which dictates how it handles updates and configuration. This prevents conflicts between different installation types.

Installation Types

• native: Installed via the native installer (preferred).
• npm-local: Installed as a local npm package (typically in ~/.claude/local).
• npm-global: Installed globally via npm.
• package-manager: Managed by system tools like Homebrew, winget, or apk.
• development: A local development build (cannot be updated via the update command).

Configuration Syncing

If your global configuration's installMethod does not match the detected installationType, the CLI will automatically update your configuration to reflect the current reality to ensure future updates use the correct mechanism.

Ultrareview usage is subject to quota and billing rules based on your subscription plan:

• Team and Enterprise Subscribers: Ultrareview is included; no free-review quota or extra usage dialogs are shown.
• Consumer Plans (Pro/Max):
  • You have a limited number of free reviews. The tool will notify you of your remaining quota (e.g., This is free ultrareview 1 of 5.).
  • Once free reviews are exhausted, you can enable Extra Usage to continue reviewing.
  • If your Extra Usage balance is very low (less than 10 credits), the tool will warn you.

If you are on a consumer plan and have exhausted your free quota, you will be prompted to confirm billing for Extra Usage. Once confirmed in a session, subsequent /ultrareview calls in that same session will proceed without re-prompting.

The marketplace management system allows for interacting with installed plugins:

• Install Plugins: Use the install action with a plugin name (e.g., install('plugin-name')) to add a plugin from a marketplace.
• Remove Plugins: Use the remove action with a plugin name (e.g., remove('plugin-name')) to uninstall a plugin.
• Update Plugins: Use the update action to update a specific plugin to its latest version.

Note: The install action requires the plugin to be present in the marketplace's available plugins list.