70cb667a2c
Updated user-facing strings throughout the TUI: Slash commands: - "instructions for Codex" → "instructions for LLMX" - "ask Codex to undo" → "ask LLMX to undo" - "exit Codex" → "exit LLMX" - "what Codex can do" → "what LLMX can do" - "log out of Codex" → "log out of LLMX" Onboarding screens: - "running Codex" → "running LLMX" - "allow Codex" → "allow LLMX" - "use Codex" → "use LLMX" - "autonomy to grant Codex" → "autonomy to grant LLMX" - "Codex can make mistakes" → "LLMX can make mistakes" - "Codex will use" → "LLMX will use" Chat composer: - "Ask Codex to do anything" → "Ask LLMX to do anything" Schema name: - "codex_output_schema" → "llmx_output_schema" Files changed: 7 files in TUI and core 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
llmx-core
This crate implements the business logic for LLMX. It is designed to be used by the various LLMX UIs written in Rust.
Dependencies
Note that llmx-core makes some assumptions about certain helper utilities being available in the environment. Currently, this support matrix is:
macOS
Expects /usr/bin/sandbox-exec to be present.
Linux
Expects the binary containing llmx-core to run the equivalent of llmx sandbox linux (legacy alias: llmx debug landlock) when arg0 is llmx-linux-sandbox. See the llmx-arg0 crate for details.
All Platforms
Expects the binary containing llmx-core to simulate the virtual apply_patch CLI when arg1 is --llmx-run-as-apply-patch. See the llmx-arg0 crate for details.