ENG-10963 refactor(log): migrate the reflex CLI and runtime to logging (3/5)

[FarhanAliRaza]

Replaces the console helper call sites with per-module loggers across reflex/, and adds shared click log options in reflex.utils.cli_options including a new --json flag that switches output to JSON-lines records (REFLEX_LOG_JSON equivalent).

Keeps a temporary LogLevel conversion mapper for the hosting CLI boundary; it is removed in the next PR when the enums unify.

Stack (ENG-10963)

#6863 → #6864 → this → hosting CLI → deprecate.
Merge in order; each PR is based on the previous branch.

[linear-code]

ENG-10963

[greptile-apps]

Greptile Summary

The PR migrates Reflex CLI and runtime output to per-module Python loggers and introduces shared logging options, including JSON-lines output.

• Replaces console helper calls across CLI, compiler, runtime, state, and utility modules.
• Centralizes Click logging options and adds --json support.
• Updates logging-related tests and command integrations.

Confidence Score: 4/5

The PR is not yet safe to merge because JSON/no-rich compilation still writes non-JSON progress lines to stdout.

The prior reply states that the issue was fixed because PoorProgress.advance goes through console.print, but the current implementation calls built-in print, providing the concrete counterexample: reflex compile --json --no-rich still interleaves Progress: N/M text with JSON records.

Files Needing Attention: reflex/compiler/compiler.py and packages/reflex-base/src/reflex_base/utils/console.py

Important Files Changed

Filename	Overview
reflex/compiler/compiler.py	Migrates compiler messages and timings to logging and changes progress construction; the previously reported JSON/no-rich progress defect remains outstanding.
reflex/utils/cli_options.py	Centralizes eager Click callbacks for log level, verbosity, and JSON mode.
reflex/reflex.py	Applies shared logging options across the main CLI and enables managed logging at the root command.
reflex/custom_components/custom_components.py	Migrates custom-component commands to module logging and shared CLI log options.
reflex/app.py	Replaces runtime console calls with a module logger across exception, page, and socket handling.

_{Reviews (11): Last reviewed commit: "fix(istate): resolve the disk states dir..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 27 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing farhan/eng-10963-log-3-migrate-core (89a637c) with main (d881ab2)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 29505c0626

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[cubic-dev-ai]

4 issues found across 39 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="reflex/reflex.py">

<violation number="1" location="reflex/reflex.py:96">
P2: The `login` command now exposes `--json` via `@log_options`, but it delegates to `reflex_cli.v2.cli.login()`, which prints through `reflex_cli.utils.console` (Rich's `_console.print`) and never checks the JSON log mode. Running `reflex login --json` will mix plain-text hosting CLI output with JSON-lines records, breaking JSON-lines consumers. Consider bridging/migrating the hosting console before exposing `--json` on hosting-backed commands, or withhold the option there until the hosting CLI is migrated.</violation>

<violation number="2" location="reflex/reflex.py:717">
P2: `reflex db` commands cannot accept the new `--json` flag, so their migrated log output is only JSON-capable through the environment variable. Apply `log_options` to the database subcommands (or provide equivalent group-level options) so CLI JSON output covers this command family.</violation>
</file>

<file name="tests/units/utils/test_utils.py">

<violation number="1" location="tests/units/utils/test_utils.py:790">
P2: This test no longer exercises the debug path it intends to. `output_system_info()` gates its body on `console.is_debug()` (`reflex_base.utils.console.is_debug`), which reads `console._LOG_LEVEL` — not `log._log_level`. The old test patched `reflex_base.utils.console._LOG_LEVEL` directly; the new one patches `reflex_base.utils.log._log_level`, which is a separate module global that only changes when `console.set_log_level()` is called. As a result `console.is_debug()` still returns `False` (default INFO), so `output_system_info()` returns early and the imports/iteration under the debug branch are no longer covered. The test still passes (its only assertion is that it doesn't crash), silently reducing coverage.</violation>
</file>

<file name="reflex/compiler/compiler.py">

<violation number="1" location="reflex/compiler/compiler.py:1191">
P2: When `reflex compile` is run with `--json --no-rich`, `console.PoorProgress()` is selected as the fallback progress renderer, and its `advance` method writes plain-text `Progress: N/M` lines directly to stdout. This mixes non-JSON text into the output stream expected to be JSON-lines, breaking machine parsing for `--json` consumers.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 3 files (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>