LAM-1968: Claude Code and Codex plugin docs

[laminar-coding-agent]

Why

The new lmnr-cli plugin add <agent> installer (lmnr-ts #279, shipped in lmnr-cli 0.3.2) makes tracing Claude Code and Codex CLI sessions a one-command setup, but neither agent had an integration page. These are the two most popular coding agents, so they should be front and center in the integrations list.

What

• New tracing/integrations/claude-code.mdx and tracing/integrations/codex.mdx: what Laminar captures (one trace per turn, LLM calls, tool executions, subagents for Claude Code, session grouping), the npx lmnr-cli@latest plugin add <agent> install flow, per-agent activation (/reload-plugins vs restart), manual marketplace install (claude plugin install lmnr@lmnr --scope user / codex plugin add lmnr@lmnr), the ~/.config/lmnr/<agent>-plugin.json config contract with env overrides, and troubleshooting.
• Self-hoster note on each page (explicitly requested): plugin add --frontend-url <issuer> --base-url <api> works against any instance; the plugin's baseUrl must carry the API port (e.g. http://localhost:8000 for Docker Compose) because the plugin POSTs to <baseUrl>/v1/traces. Repeated in the Troubleshooting accordion with the edit-the-config-file recovery path.
• Navigation: both pages added to docs.json and to the Coding agents section of the integrations overview, listed before Claude Agent SDK / OpenCode.
• Changelog: July 2026 entry for the plugins.
• CLAUDE.md: recorded the non-obvious invariants (install ref is lmnr@lmnr for both agents; the Claude plugin repo README's laminar@laminar is stale; baseUrl includes the port unlike the SDK's split; per-agent activation differences).

Verification

• Install commands, flags, config filenames, and marketplace refs verified against the published lmnr-cli@0.3.2 npm artifact (plugin add --help output and bundled AGENTS registry), not just the repo source.
• Plugin behavior (config precedence, /v1/traces endpoint, fail-open, session grouping, LMNR_USER_ID attribution) verified against both plugin repos' source.
• npx mintlify broken-links passes; no em dashes or banned vocabulary.

Facts I could not verify end-to-end

• Did not run a live plugin add install (no claude/codex host CLI in the sandbox); the printed-commands fallback path is documented from the CLI source and --help output.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes with no application or API code; incorrect install flags would confuse users but do not affect production systems.

Overview
Adds public docs for tracing Claude Code and OpenAI Codex CLI via the lmnr-cli plugin add flow (LAM-1968).

New pages tracing/integrations/claude-code.mdx and tracing/integrations/codex.mdx describe one-command install (npx lmnr-cli@latest plugin add claude-code|codex), global config at ~/.config/lmnr/<agent>-plugin.json, manual marketplace install (lmnr@lmnr), env overrides, and self-hosted --frontend-url / --base-url (API URL must include the port). Activation differs: Claude Code uses /reload-plugins or a new terminal; Codex requires a restart.

docs.json and the Coding agents section on tracing/integrations/overview.mdx list both integrations first, ahead of Claude Agent SDK and OpenCode. changelog.mdx gets a July 2026 entry. CLAUDE.md records maintainer invariants (canonical lmnr@lmnr ref, no legacy Codex install path, baseUrl includes port).

^{Reviewed by Cursor Bugbot for commit 988c4c2. Bugbot is set up for automated code reviews on this repo. Configure here.}