This release represents a comprehensive transformation of the codebase from Codex to LLMX, enhanced with LiteLLM integration to support 100+ LLM providers through a unified API. ## Major Changes ### Phase 1: Repository & Infrastructure Setup - Established new repository structure and branching strategy - Created comprehensive project documentation (CLAUDE.md, LITELLM-SETUP.md) - Set up development environment and tooling configuration ### Phase 2: Rust Workspace Transformation - Renamed all Rust crates from `codex-*` to `llmx-*` (30+ crates) - Updated package names, binary names, and workspace members - Renamed core modules: codex.rs → llmx.rs, codex_delegate.rs → llmx_delegate.rs - Updated all internal references, imports, and type names - Renamed directories: codex-rs/ → llmx-rs/, codex-backend-openapi-models/ → llmx-backend-openapi-models/ - Fixed all Rust compilation errors after mass rename ### Phase 3: LiteLLM Integration - Integrated LiteLLM for multi-provider LLM support (Anthropic, OpenAI, Azure, Google AI, AWS Bedrock, etc.) - Implemented OpenAI-compatible Chat Completions API support - Added model family detection and provider-specific handling - Updated authentication to support LiteLLM API keys - Renamed environment variables: OPENAI_BASE_URL → LLMX_BASE_URL - Added LLMX_API_KEY for unified authentication - Enhanced error handling for Chat Completions API responses - Implemented fallback mechanisms between Responses API and Chat Completions API ### Phase 4: TypeScript/Node.js Components - Renamed npm package: @codex/codex-cli → @valknar/llmx - Updated TypeScript SDK to use new LLMX APIs and endpoints - Fixed all TypeScript compilation and linting errors - Updated SDK tests to support both API backends - Enhanced mock server to handle multiple API formats - Updated build scripts for cross-platform packaging ### Phase 5: Configuration & Documentation - Updated all configuration files to use LLMX naming - Rewrote README and documentation for LLMX branding - Updated config paths: ~/.codex/ → ~/.llmx/ - Added comprehensive LiteLLM setup guide - Updated all user-facing strings and help text - Created release plan and migration documentation ### Phase 6: Testing & Validation - Fixed all Rust tests for new naming scheme - Updated snapshot tests in TUI (36 frame files) - Fixed authentication storage tests - Updated Chat Completions payload and SSE tests - Fixed SDK tests for new API endpoints - Ensured compatibility with Claude Sonnet 4.5 model - Fixed test environment variables (LLMX_API_KEY, LLMX_BASE_URL) ### Phase 7: Build & Release Pipeline - Updated GitHub Actions workflows for LLMX binary names - Fixed rust-release.yml to reference llmx-rs/ instead of codex-rs/ - Updated CI/CD pipelines for new package names - Made Apple code signing optional in release workflow - Enhanced npm packaging resilience for partial platform builds - Added Windows sandbox support to workspace - Updated dotslash configuration for new binary names ### Phase 8: Final Polish - Renamed all assets (.github images, labels, templates) - Updated VSCode and DevContainer configurations - Fixed all clippy warnings and formatting issues - Applied cargo fmt and prettier formatting across codebase - Updated issue templates and pull request templates - Fixed all remaining UI text references ## Technical Details **Breaking Changes:** - Binary name changed from `codex` to `llmx` - Config directory changed from `~/.codex/` to `~/.llmx/` - Environment variables renamed (CODEX_* → LLMX_*) - npm package renamed to `@valknar/llmx` **New Features:** - Support for 100+ LLM providers via LiteLLM - Unified authentication with LLMX_API_KEY - Enhanced model provider detection and handling - Improved error handling and fallback mechanisms **Files Changed:** - 578 files modified across Rust, TypeScript, and documentation - 30+ Rust crates renamed and updated - Complete rebrand of UI, CLI, and documentation - All tests updated and passing **Dependencies:** - Updated Cargo.lock with new package names - Updated npm dependencies in llmx-cli - Enhanced OpenAPI models for LLMX backend This release establishes LLMX as a standalone project with comprehensive LiteLLM integration, maintaining full backward compatibility with existing functionality while opening support for a wide ecosystem of LLM providers. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: Sebastian Krüger <support@pivoine.art>
178 lines
4.9 KiB
JavaScript
178 lines
4.9 KiB
JavaScript
#!/usr/bin/env node
|
|
// Unified entry point for the LLMX CLI.
|
|
|
|
import { spawn } from "node:child_process";
|
|
import { existsSync } from "fs";
|
|
import path from "path";
|
|
import { fileURLToPath } from "url";
|
|
|
|
// __dirname equivalent in ESM
|
|
const __filename = fileURLToPath(import.meta.url);
|
|
const __dirname = path.dirname(__filename);
|
|
|
|
const { platform, arch } = process;
|
|
|
|
let targetTriple = null;
|
|
switch (platform) {
|
|
case "linux":
|
|
case "android":
|
|
switch (arch) {
|
|
case "x64":
|
|
targetTriple = "x86_64-unknown-linux-musl";
|
|
break;
|
|
case "arm64":
|
|
targetTriple = "aarch64-unknown-linux-musl";
|
|
break;
|
|
default:
|
|
break;
|
|
}
|
|
break;
|
|
case "darwin":
|
|
switch (arch) {
|
|
case "x64":
|
|
targetTriple = "x86_64-apple-darwin";
|
|
break;
|
|
case "arm64":
|
|
targetTriple = "aarch64-apple-darwin";
|
|
break;
|
|
default:
|
|
break;
|
|
}
|
|
break;
|
|
case "win32":
|
|
switch (arch) {
|
|
case "x64":
|
|
targetTriple = "x86_64-pc-windows-msvc";
|
|
break;
|
|
case "arm64":
|
|
targetTriple = "aarch64-pc-windows-msvc";
|
|
break;
|
|
default:
|
|
break;
|
|
}
|
|
break;
|
|
default:
|
|
break;
|
|
}
|
|
|
|
if (!targetTriple) {
|
|
throw new Error(`Unsupported platform: ${platform} (${arch})`);
|
|
}
|
|
|
|
const vendorRoot = path.join(__dirname, "..", "vendor");
|
|
const archRoot = path.join(vendorRoot, targetTriple);
|
|
const llmxBinaryName = process.platform === "win32" ? "llmx.exe" : "llmx";
|
|
const binaryPath = path.join(archRoot, "llmx", llmxBinaryName);
|
|
|
|
// Use an asynchronous spawn instead of spawnSync so that Node is able to
|
|
// respond to signals (e.g. Ctrl-C / SIGINT) while the native binary is
|
|
// executing. This allows us to forward those signals to the child process
|
|
// and guarantees that when either the child terminates or the parent
|
|
// receives a fatal signal, both processes exit in a predictable manner.
|
|
|
|
function getUpdatedPath(newDirs) {
|
|
const pathSep = process.platform === "win32" ? ";" : ":";
|
|
const existingPath = process.env.PATH || "";
|
|
const updatedPath = [
|
|
...newDirs,
|
|
...existingPath.split(pathSep).filter(Boolean),
|
|
].join(pathSep);
|
|
return updatedPath;
|
|
}
|
|
|
|
/**
|
|
* Use heuristics to detect the package manager that was used to install LLMX
|
|
* in order to give the user a hint about how to update it.
|
|
*/
|
|
function detectPackageManager() {
|
|
const userAgent = process.env.npm_config_user_agent || "";
|
|
if (/\bbun\//.test(userAgent)) {
|
|
return "bun";
|
|
}
|
|
|
|
const execPath = process.env.npm_execpath || "";
|
|
if (execPath.includes("bun")) {
|
|
return "bun";
|
|
}
|
|
|
|
if (
|
|
process.env.BUN_INSTALL ||
|
|
process.env.BUN_INSTALL_GLOBAL_DIR ||
|
|
process.env.BUN_INSTALL_BIN_DIR
|
|
) {
|
|
return "bun";
|
|
}
|
|
|
|
return userAgent ? "npm" : null;
|
|
}
|
|
|
|
const additionalDirs = [];
|
|
const pathDir = path.join(archRoot, "path");
|
|
if (existsSync(pathDir)) {
|
|
additionalDirs.push(pathDir);
|
|
}
|
|
const updatedPath = getUpdatedPath(additionalDirs);
|
|
|
|
const env = { ...process.env, PATH: updatedPath };
|
|
const packageManagerEnvVar =
|
|
detectPackageManager() === "bun"
|
|
? "LLMX_MANAGED_BY_BUN"
|
|
: "LLMX_MANAGED_BY_NPM";
|
|
env[packageManagerEnvVar] = "1";
|
|
|
|
const child = spawn(binaryPath, process.argv.slice(2), {
|
|
stdio: "inherit",
|
|
env,
|
|
});
|
|
|
|
child.on("error", (err) => {
|
|
// Typically triggered when the binary is missing or not executable.
|
|
// Re-throwing here will terminate the parent with a non-zero exit code
|
|
// while still printing a helpful stack trace.
|
|
// eslint-disable-next-line no-console
|
|
console.error(err);
|
|
process.exit(1);
|
|
});
|
|
|
|
// Forward common termination signals to the child so that it shuts down
|
|
// gracefully. In the handler we temporarily disable the default behavior of
|
|
// exiting immediately; once the child has been signaled we simply wait for
|
|
// its exit event which will in turn terminate the parent (see below).
|
|
const forwardSignal = (signal) => {
|
|
if (child.killed) {
|
|
return;
|
|
}
|
|
try {
|
|
child.kill(signal);
|
|
} catch {
|
|
/* ignore */
|
|
}
|
|
};
|
|
|
|
["SIGINT", "SIGTERM", "SIGHUP"].forEach((sig) => {
|
|
process.on(sig, () => forwardSignal(sig));
|
|
});
|
|
|
|
// When the child exits, mirror its termination reason in the parent so that
|
|
// shell scripts and other tooling observe the correct exit status.
|
|
// Wrap the lifetime of the child process in a Promise so that we can await
|
|
// its termination in a structured way. The Promise resolves with an object
|
|
// describing how the child exited: either via exit code or due to a signal.
|
|
const childResult = await new Promise((resolve) => {
|
|
child.on("exit", (code, signal) => {
|
|
if (signal) {
|
|
resolve({ type: "signal", signal });
|
|
} else {
|
|
resolve({ type: "code", exitCode: code ?? 1 });
|
|
}
|
|
});
|
|
});
|
|
|
|
if (childResult.type === "signal") {
|
|
// Re-emit the same signal so that the parent terminates with the expected
|
|
// semantics (this also sets the correct exit code of 128 + n).
|
|
process.kill(process.pid, childResult.signal);
|
|
} else {
|
|
process.exit(childResult.exitCode);
|
|
}
|