Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/features/cli-backend.mdx`:
- Around line 121-122: The table header uses "Purpose" instead of the required
"Description"; update the table header row so the columns read "Option | Type |
Default | Description" (replace the "Purpose" column), and scan the surrounding
content for any other instances of the "Purpose" column in this docs block to
ensure the documentation follows the required config table schema for SDK config
options.
- Line 288: Replace the relative link './claude-cli#installation' in the CLI
backend docs line with the absolute docs route so the link resolves correctly
from anywhere; specifically locate the string './claude-cli#installation' in
docs/features/cli-backend.mdx and change it to the absolute path (for example
'/docs/features/claude-cli#installation') ensuring the anchor '#installation' is
preserved.
- Around line 35-44: The first Quick Start code block exceeds the 6-line limit;
compress it to a minimal runnable snippet by collapsing the multi-line Agent
construction into a single line and keeping the agent.start call on the next
line—update the usage of Agent and agent.start (and the cli_backend parameter)
so the snippet becomes two concise lines while preserving the same arguments and
behavior.
- Around line 8-33: Add an agent-first code example at the very top of
docs/features/cli-backend.mdx (before the mermaid diagram and any prose) that
demonstrates an agent invoking the CLI Backend (e.g., using the "CLI Backend" to
call the "claude CLI") so the page starts with a concrete agent-centric usage
snippet; update the "Simple Usage" Step if present to reference this new snippet
and ensure the agent example shows inputs, invocation of the backend, and
expected result so readers see the agent perspective immediately.
- Around line 176-190: The example misdocuments backend wiring for Agent by
importing Agent from praisonaiagents while relying on string-ID auto-resolution
provided by the praisonai wrapper; fix by making the example consistent: either
import Agent from praisonai (e.g., use the praisonai wrapper import instead of
praisonaiagents) or keep the praisonaiagents import and explicitly resolve/pass
the backend (resolve the backend ID via the praisonai wrapper or factory and
pass the resolved backend object into Agent via the cli_backend parameter);
update the snippet to use the Agent symbol with a correctly-resolved backend
(cli_backend) so the docs match runtime behavior.
- Around line 216-235: The example is missing the Agent import so it isn't
runnable; update the snippet to include the required import(s) at the top (e.g.,
import Agent from the library) so the final lines using
Agent(cli_backend="my-cli") work; ensure the header imports include Agent plus
the existing CliBackendConfig, CliBackendProtocol and register_cli_backend
references and keep the MyCustomBackend, register_cli_backend("my-cli", ...) and
Agent(...) symbols unchanged so the example runs as-is.
- Around line 117-167: Add explicit documentation blocks covering (1) the
two-import behavior: describe the TypeError thrown when both imports are used,
how to detect it and the recommended fixes (use only praissonaiagents or
praisonai or adjust import order), (2) a complete exported-symbols list for both
praissonaiagents and praisonai (enumerate public classes/functions), and (3)
detailed agent wiring: explain session-id logic (session_arg, session_mode,
session_id_fields), system prompt composition (system_prompt_arg,
system_prompt_when, system_prompt_mode), image extraction rules (image_arg,
image_mode), how backend.execute(...) is invoked, and the RuntimeError path and
when it is raised; include examples or expected error messages for each to
satisfy the PR objectives.

---

Nitpick comments:
In `@docs/cli/claude-cli.mdx`:
- Around line 195-214: The Python Integration example should be updated to match
the new CLI Backend exports: replace usage of the nested ClaudeCodeIntegration
with the public SDK export(s) such as ClaudeCodeBackend or the
resolve_cli_backend helper and adjust method names accordingly (e.g., use
ClaudeCodeBackend(...).execute / .stream or resolve_cli_backend(...) to obtain a
backend instance). Update the import line to import from praisonai directly
(e.g., import ClaudeCodeBackend or resolve_cli_backend) and ensure the example
shows how to create the backend with workspace, output_format, and model, then
call execute and stream on that backend.

In `@docs/features/cli-backend.mdx`:
- Around line 49-51: Replace nested-module imports with top-level SDK imports in
the examples: change imports that use praisonai.cli_backends to import the
public helpers directly (use resolve_cli_backend and register_cli_backend from
praisonai) so examples show "from praisonai import resolve_cli_backend,
register_cli_backend" (and keep Agent imported as "from praisonai import Agent"
where shown); update all occurrences referenced (around lines noted) so
documentation consistently demonstrates the top-level API surface instead of
praisonai.cli_backends.