Use Lithi with Codex

Codex can assess a bounded task for Lithi Compute and use the customer Work tools after you connect an approved account. Codex retains your project context; you decide whether to submit work and how to use its result.

Choose a task with Codex

Ask Codex to identify a repeatable part of the work, the allowed inputs, the output contract and a way to check the answer. For a first test, select one fixed diff and its relevant callers. Ask for source-linked findings against a stated review rubric; keep edits, builds and tests local. Compare the proposed work with keeping the review in Codex. Usage fit helps you consider that choice.

Assess this fixed diff and its supplied callers for a supported Compute review. Propose a bounded test that returns findings with source references and explains any uncertainty. Keep edits, builds and tests local; ask before transferring data or spending.

Suitable offloaded work may preserve subscription allowance for later work. For direct API charges or purchased credits, compare equivalent costs instead. Codex reasoning and review, including tool output it processes, still use host capacity. Consult current Codex pricing for the terms that apply to you.

Connect and verify your account

Check Compute access approval, then use the host's current MCP setup documentation for your approved connection. .codex/config.toml is a project configuration location, not permission to modify it. Use your account-issued endpoint and a protected credential reference supported by Codex; never put a secret in a prompt, example, command argument or project file.

Verify the session uses the intended account and scopes. A host instruction or skill does not grant access, approve a transfer or authorize paid execution. See the MCP guide for the account boundary.

Run a bounded synthetic test

Check that the connection exposes exactly five customer Work tools: lithi.quote, lithi.run, lithi.batch, lithi.status and lithi.result. The first prices a request, the next two request execution, and the last two read job state and result metadata. Account management and reporting are separate.

Discover a supported operation and prepare the permitted diff and callers in its accepted format. If the account needs credit, complete the secure browser funding step yourself and confirm the credit on the same account. Request a quote for the bounded test, then obtain the required transfer and spend approvals before submitting. Even a synthetic submission can use paid credit. Your first test offers a fuller path through the decision.

Review the result and recover the same job

Read the existing job with lithi.status and use lithi.result when it is ready. The latter returns bounded metadata identifying authorized result files, not plaintext result rows. Retrieve authorized files and verify the digest, then check each finding against the fixed diff and cited caller; see result verification. After an uncertain submission or timeout, inspect the same job and retain the original request intent and idempotency key. Follow its next action rather than submitting a replacement just to recover it.