feat: Complete LLMX v0.1.0 - Rebrand from Codex with LiteLLM Integration
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>
2025-11-12 20:40:44 +01:00
|
|
|
extern crate llmx_execpolicy;
|
2025-04-24 17:14:47 -07:00
|
|
|
|
feat: Complete LLMX v0.1.0 - Rebrand from Codex with LiteLLM Integration
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>
2025-11-12 20:40:44 +01:00
|
|
|
use llmx_execpolicy::ArgType;
|
|
|
|
|
use llmx_execpolicy::Error;
|
|
|
|
|
use llmx_execpolicy::ExecCall;
|
|
|
|
|
use llmx_execpolicy::MatchedArg;
|
|
|
|
|
use llmx_execpolicy::MatchedExec;
|
|
|
|
|
use llmx_execpolicy::MatchedFlag;
|
|
|
|
|
use llmx_execpolicy::Policy;
|
|
|
|
|
use llmx_execpolicy::Result;
|
|
|
|
|
use llmx_execpolicy::ValidExec;
|
|
|
|
|
use llmx_execpolicy::get_default_policy;
|
2025-04-24 17:14:47 -07:00
|
|
|
|
2025-08-14 17:59:01 -07:00
|
|
|
#[expect(clippy::expect_used)]
|
2025-04-24 17:14:47 -07:00
|
|
|
fn setup() -> Policy {
|
|
|
|
|
get_default_policy().expect("failed to load default policy")
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_ls_no_args() {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
let ls = ExecCall::new("ls", &[]);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Ok(MatchedExec::Match {
|
|
|
|
|
exec: ValidExec::new("ls", vec![], &["/bin/ls", "/usr/bin/ls"])
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls)
|
|
|
|
|
);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_ls_dash_a_dash_l() {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
let args = &["-a", "-l"];
|
|
|
|
|
let ls_a_l = ExecCall::new("ls", args);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Ok(MatchedExec::Match {
|
|
|
|
|
exec: ValidExec {
|
|
|
|
|
program: "ls".into(),
|
|
|
|
|
flags: vec![MatchedFlag::new("-a"), MatchedFlag::new("-l")],
|
|
|
|
|
system_path: ["/bin/ls".into(), "/usr/bin/ls".into()].into(),
|
|
|
|
|
..Default::default()
|
|
|
|
|
}
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls_a_l)
|
|
|
|
|
);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_ls_dash_z() {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
|
|
|
|
|
// -z is currently an invalid option for ls, but it has so many options,
|
|
|
|
|
// perhaps it will get added at some point...
|
|
|
|
|
let ls_z = ExecCall::new("ls", &["-z"]);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Err(Error::UnknownOption {
|
|
|
|
|
program: "ls".into(),
|
|
|
|
|
option: "-z".into()
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls_z)
|
|
|
|
|
);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_ls_dash_al() {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
|
|
|
|
|
// This currently fails, but it should pass once option_bundling=True is implemented.
|
|
|
|
|
let ls_al = ExecCall::new("ls", &["-al"]);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Err(Error::UnknownOption {
|
|
|
|
|
program: "ls".into(),
|
|
|
|
|
option: "-al".into()
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls_al)
|
|
|
|
|
);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_ls_one_file_arg() -> Result<()> {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
|
|
|
|
|
let ls_one_file_arg = ExecCall::new("ls", &["foo"]);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Ok(MatchedExec::Match {
|
|
|
|
|
exec: ValidExec::new(
|
|
|
|
|
"ls",
|
|
|
|
|
vec![MatchedArg::new(0, ArgType::ReadableFile, "foo")?],
|
|
|
|
|
&["/bin/ls", "/usr/bin/ls"]
|
|
|
|
|
)
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls_one_file_arg)
|
|
|
|
|
);
|
|
|
|
|
Ok(())
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_ls_multiple_file_args() -> Result<()> {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
|
|
|
|
|
let ls_multiple_file_args = ExecCall::new("ls", &["foo", "bar", "baz"]);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Ok(MatchedExec::Match {
|
|
|
|
|
exec: ValidExec::new(
|
|
|
|
|
"ls",
|
|
|
|
|
vec![
|
|
|
|
|
MatchedArg::new(0, ArgType::ReadableFile, "foo")?,
|
|
|
|
|
MatchedArg::new(1, ArgType::ReadableFile, "bar")?,
|
|
|
|
|
MatchedArg::new(2, ArgType::ReadableFile, "baz")?,
|
|
|
|
|
],
|
|
|
|
|
&["/bin/ls", "/usr/bin/ls"]
|
|
|
|
|
)
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls_multiple_file_args)
|
|
|
|
|
);
|
|
|
|
|
Ok(())
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_ls_multiple_flags_and_file_args() -> Result<()> {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
|
|
|
|
|
let ls_multiple_flags_and_file_args = ExecCall::new("ls", &["-l", "-a", "foo", "bar", "baz"]);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Ok(MatchedExec::Match {
|
|
|
|
|
exec: ValidExec {
|
|
|
|
|
program: "ls".into(),
|
|
|
|
|
flags: vec![MatchedFlag::new("-l"), MatchedFlag::new("-a")],
|
|
|
|
|
args: vec![
|
|
|
|
|
MatchedArg::new(2, ArgType::ReadableFile, "foo")?,
|
|
|
|
|
MatchedArg::new(3, ArgType::ReadableFile, "bar")?,
|
|
|
|
|
MatchedArg::new(4, ArgType::ReadableFile, "baz")?,
|
|
|
|
|
],
|
|
|
|
|
system_path: ["/bin/ls".into(), "/usr/bin/ls".into()].into(),
|
|
|
|
|
..Default::default()
|
|
|
|
|
}
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls_multiple_flags_and_file_args)
|
|
|
|
|
);
|
|
|
|
|
Ok(())
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
fn test_flags_after_file_args() -> Result<()> {
|
|
|
|
|
let policy = setup();
|
|
|
|
|
|
|
|
|
|
// TODO(mbolin): While this is "safe" in that it will not do anything bad
|
|
|
|
|
// to the user's machine, it will fail because apparently `ls` does not
|
|
|
|
|
// allow flags after file arguments (as some commands do). We should
|
|
|
|
|
// extend define_program() to make this part of the configuration so that
|
|
|
|
|
// this command is disallowed.
|
|
|
|
|
let ls_flags_after_file_args = ExecCall::new("ls", &["foo", "-l"]);
|
|
|
|
|
assert_eq!(
|
|
|
|
|
Ok(MatchedExec::Match {
|
|
|
|
|
exec: ValidExec {
|
|
|
|
|
program: "ls".into(),
|
|
|
|
|
flags: vec![MatchedFlag::new("-l")],
|
|
|
|
|
args: vec![MatchedArg::new(0, ArgType::ReadableFile, "foo")?],
|
|
|
|
|
system_path: ["/bin/ls".into(), "/usr/bin/ls".into()].into(),
|
|
|
|
|
..Default::default()
|
|
|
|
|
}
|
|
|
|
|
}),
|
|
|
|
|
policy.check(&ls_flags_after_file_args)
|
|
|
|
|
);
|
|
|
|
|
Ok(())
|
|
|
|
|
}
|