Updated all documentation and configuration files: Documentation changes: - Updated README.md to describe LLMX as LiteLLM-powered fork - Updated CLAUDE.md with LiteLLM integration details - Updated 50+ markdown files across docs/, llmx-rs/, llmx-cli/, sdk/ - Changed all references: codex → llmx, Codex → LLMX - Updated package references: @openai/codex → @llmx/llmx - Updated repository URLs: github.com/openai/codex → github.com/valknar/llmx Configuration changes: - Updated .github/dependabot.yaml - Updated .github workflow files - Updated cliff.toml (changelog configuration) - Updated Cargo.toml comments Key branding updates: - Project description: "coding agent from OpenAI" → "coding agent powered by LiteLLM" - Added attribution to original OpenAI Codex project - Documented LiteLLM integration benefits Files changed: 51 files (559 insertions, 559 deletions) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
5.7 KiB
Getting started
Looking for something specific? Jump ahead:
- Tips & shortcuts – hotkeys, resume flow, prompts
- Non-interactive runs – automate with
llmx exec - Ready for deeper customization? Head to
advanced.md
CLI usage
| Command | Purpose | Example |
|---|---|---|
llmx |
Interactive TUI | llmx |
llmx "..." |
Initial prompt for interactive TUI | llmx "fix lint errors" |
llmx exec "..." |
Non-interactive "automation mode" | llmx exec "explain utils.ts" |
Key flags: --model/-m, --ask-for-approval/-a.
Resuming interactive sessions
- Run
llmx resumeto display the session picker UI - Resume most recent:
llmx resume --last - Resume by id:
llmx resume <SESSION_ID>(You can get session ids from /status or~/.llmx/sessions/)
Examples:
# Open a picker of recent sessions
llmx resume
# Resume the most recent session
llmx resume --last
# Resume a specific session by id
llmx resume 7f9f9a2e-1b3c-4c7a-9b0e-123456789abc
Running with a prompt as input
You can also run LLMX CLI with a prompt as input:
llmx "explain this codebase to me"
Example prompts
Below are a few bite-size examples you can copy-paste. Replace the text in quotes with your own task.
| ✨ | What you type | What happens |
|---|---|---|
| 1 | llmx "Refactor the Dashboard component to React Hooks" |
LLMX rewrites the class component, runs npm test, and shows the diff. |
| 2 | llmx "Generate SQL migrations for adding a users table" |
Infers your ORM, creates migration files, and runs them in a sandboxed DB. |
| 3 | llmx "Write unit tests for utils/date.ts" |
Generates tests, executes them, and iterates until they pass. |
| 4 | llmx "Bulk-rename *.jpeg -> *.jpg with git mv" |
Safely renames files and updates imports/usages. |
| 5 | llmx "Explain what this regex does: ^(?=.*[A-Z]).{8,}$" |
Outputs a step-by-step human explanation. |
| 6 | llmx "Carefully review this repo, and propose 3 high impact well-scoped PRs" |
Suggests impactful PRs in the current codebase. |
| 7 | llmx "Look for vulnerabilities and create a security review report" |
Finds and explains security bugs. |
Looking to reuse your own instructions? Create slash commands with custom prompts.
Memory with AGENTS.md
You can give LLMX extra instructions and guidance using AGENTS.md files. LLMX looks for them in the following places, and merges them top-down:
~/.llmx/AGENTS.md- personal global guidance- Every directory from the repository root down to your current working directory (inclusive). In each directory, LLMX first looks for
AGENTS.override.mdand uses it if present; otherwise it falls back toAGENTS.md. Use the override form when you want to replace inherited instructions for that directory.
For more information on how to use AGENTS.md, see the official AGENTS.md documentation.
Tips & shortcuts
Use @ for file search
Typing @ triggers a fuzzy-filename search over the workspace root. Use up/down to select among the results and Tab or Enter to replace the @ with the selected path. You can use Esc to cancel the search.
Esc–Esc to edit a previous message
When the chat composer is empty, press Esc to prime “backtrack” mode. Press Esc again to open a transcript preview highlighting the last user message; press Esc repeatedly to step to older user messages. Press Enter to confirm and LLMX will fork the conversation from that point, trim the visible transcript accordingly, and pre‑fill the composer with the selected user message so you can edit and resubmit it.
In the transcript preview, the footer shows an Esc edit prev hint while editing is active.
--cd/-C flag
Sometimes it is not convenient to cd to the directory you want LLMX to use as the "working root" before running LLMX. Fortunately, llmx supports a --cd option so you can specify whatever folder you want. You can confirm that LLMX is honoring --cd by double-checking the workdir it reports in the TUI at the start of a new session.
--add-dir flag
Need to work across multiple projects in one run? Pass --add-dir one or more times to expose extra directories as writable roots for the current session while keeping the main working directory unchanged. For example:
llmx --cd apps/frontend --add-dir ../backend --add-dir ../shared
LLMX can then inspect and edit files in each listed directory without leaving the primary workspace.
Shell completions
Generate shell completion scripts via:
llmx completion bash
llmx completion zsh
llmx completion fish
Image input
Paste images directly into the composer (Ctrl+V / Cmd+V) to attach them to your prompt. You can also attach files via the CLI using -i/--image (comma‑separated):
llmx -i screenshot.png "Explain this error"
llmx --image img1.png,img2.jpg "Summarize these diagrams"