Files

Sebastian Krüger 831e6fa6b5 Complete comprehensive Codex → LLMX branding update

Fixed all remaining user-facing "Codex" references across entire codebase:
- Updated all UI strings and error messages
- Fixed GitHub issue templates and workflows
- Updated MCP server tool descriptions and error messages
- Fixed all test messages and comments
- Updated documentation comments
- Changed auth keyring service name to "LLMX Auth"

Reduced from 201 occurrences to only code identifiers (struct/type names).
Changes span 78 files across Rust, Python, YAML, and JSON.

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-11 16:01:04 +01:00

devcontainer.json

Complete comprehensive Codex → LLMX branding update

2025-11-11 16:01:04 +01:00

Dockerfile

chore: install just in the devcontainer for Linux development (#1375 )

2025-06-24 17:20:53 -07:00

README.md

Phase 5: Configuration & Documentation

2025-11-11 14:45:40 +01:00

README.md

Containerized Development

We provide the following options to facilitate LLMX development in a container. This is particularly useful for verifying the Linux build when working on a macOS host.

Docker

To build the Docker image locally for x64 and then run it with the repo mounted under /workspace:

CODEX_DOCKER_IMAGE_NAME=llmx-linux-dev
docker build --platform=linux/amd64 -t "$CODEX_DOCKER_IMAGE_NAME" ./.devcontainer
docker run --platform=linux/amd64 --rm -it -e CARGO_TARGET_DIR=/workspace/llmx-rs/target-amd64 -v "$PWD":/workspace -w /workspace/llmx-rs "$CODEX_DOCKER_IMAGE_NAME"

Note that /workspace/target will contain the binaries built for your host platform, so we include -e CARGO_TARGET_DIR=/workspace/llmx-rs/target-amd64 in the docker run command so that the binaries built inside your container are written to a separate directory.

For arm64, specify --platform=linux/amd64 instead for both docker build and docker run.

Currently, the Dockerfile works for both x64 and arm64 Linux, though you need to run rustup target add x86_64-unknown-linux-musl yourself to install the musl toolchain for x64.

VS Code

VS Code recognizes the devcontainer.json file and gives you the option to develop LLMX in a container. Currently, devcontainer.json builds and runs the arm64 flavor of the container.

From the integrated terminal in VS Code, you can build either flavor of the arm64 build (GNU or musl):

cargo build --target aarch64-unknown-linux-musl
cargo build --target aarch64-unknown-linux-gnu