ENG-10963 refactor(log): hosting CLI shares the reflex-base console and logging (4/5)

[FarhanAliRaza]

reflex-hosting-cli now depends on reflex-base: its forked console module and LogLevel enum become shims over the shared ones, and its logging goes through standard python logging.

• The base console.ask gains the same str-typed overloads the forked console had (the flat str | None signature broke typing at the hosting call sites).
• Intentional behavior deltas: debug output renders purple (was blue), errors go to stderr (was stdout), success messages are hidden at --loglevel warning.
• The temporary LogLevel conversion mapper in reflex/reflex.py is removed.
• The hosting-cli dev pin (reflex-base >= 0.9.8.post19.dev0) must be re-pinned at the 0.9.9 release.

Stack (ENG-10963)

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

[linear-code]

ENG-10963

[greptile-apps]

Greptile Summary

The PR consolidates hosting CLI console and logging behavior onto reflex-base and removes the temporary LogLevel conversion layer.

• Adds reflex-base as a hosting CLI dependency and replaces the forked console and LogLevel implementations with compatibility shims.
• Routes hosting diagnostics through standard Python logging, including the shared SUCCESS level.
• Extends the shared console prompt typing and table-overflow configuration.
• Updates hosting CLI tests for the shared logging behavior and removes the top-level LogLevel mapper.

Confidence Score: 5/5

The PR appears safe to merge because no blocking failure remains in the eligible follow-up review scope.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/reflex-base/src/reflex_base/utils/console.py	Adds string-returning ask overloads and configurable table-cell overflow while preserving the shared console implementation.
packages/reflex-hosting-cli/src/reflex_cli/utils/console.py	Replaces the forked console implementation with reflex-base re-exports and a legacy string-compatible log-level wrapper.
packages/reflex-hosting-cli/src/reflex_cli/constants/base.py	Re-exports reflex-base's LogLevel so Reflex and the hosting CLI use the same enum class.
packages/reflex-hosting-cli/src/reflex_cli/utils/hosting.py	Migrates user diagnostics and deployment status messages from the local console helpers to standard logging.
packages/reflex-hosting-cli/src/reflex_cli/v2/cli.py	Migrates command diagnostics to standard logging and uses the shared SUCCESS level for successful operations.
packages/reflex-hosting-cli/src/reflex_cli/v2/apps.py	Routes application-management diagnostics through module logging while retaining direct console output for requested command results.
packages/reflex-hosting-cli/pyproject.toml	Adds the reflex-base runtime dependency and configures its workspace source.
reflex/reflex.py	Passes the now-shared LogLevel directly to hosting commands and removes the temporary enum conversion mapper.
uv.lock	Updates the resolved workspace dependency graph to include reflex-base for reflex-hosting-cli.

_{Reviews (13): Last reviewed commit: "chore(news): name the hosting CLI fragme..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 27 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing farhan/eng-10963-log-4-hosting-cli (bc90a38) with main (26a7834)²}

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. ↩

2. No successful run was found on main (d28be54) during the generation of this report, so 26a7834 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[cubic-dev-ai]

4 issues found across 27 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="tests/units/reflex_cli/v2/test_cli.py">

<violation number="1" location="tests/units/reflex_cli/v2/test_cli.py:18">
P2: The caplog-based assertions in the migrated tests may not capture the records they expect. caplog listens on the root logger, so it only sees records that propagate up the logger hierarchy. But cli.logout/deploy call `console.set_log_level(...)` before emitting the messages under test, and that call configures the reflex-base pipeline (reflex_base/utils/log.py `configure()`), which sets `logger.propagate = False` on the `reflex_cli` root logger and attaches its own handler. After propagation is disabled, the `logger.error`/`logger.log(SUCCESS)` records are handled by the reflex_cli handler and never reach caplog, so these assertions can return empty. Worth verifying these tests actually pass in the full suite (order-dependently they may fail once any earlier test configures the pipeline), and if so, capture at the `reflex_cli` logger level or assert via the reflex-base handler instead of the root-level caplog.</violation>
</file>

<file name="tests/units/reflex_cli/v2/test_apps.py">

<violation number="1" location="tests/units/reflex_cli/v2/test_apps.py:365">
P2: These new assertions read records off the `caplog` fixture, which captures by attaching a handler to the root logger. But the shared reflex-base logging pipeline (on which this PR switches the hosting CLI) sets `logger.propagate = False` on the `reflex_cli` package-root logger (and `reflex_base`), so records emitted by `reflex_cli.v2.apps` never reach the root logger. If the pipeline's `bootstrap()`/`configure()` runs during the test (the commands call `console.set_log_level`, which routes into reflex_base logging), `caplog.records` will be empty and the strict equality asserts like `errors == ["get status failed: Invalid token"]` / `warnings == ["..."]` will fail (or, with `in`/`[-1]` checks, pass vacuously). Consider capturing from the `reflex_cli` logger directly (e.g. `caplog.set_level(..., logger="reflex_cli")`), or verify in the test env that propagation is not disabled, so the assertions actually observe the records.</violation>
</file>

<file name="tests/units/reflex_cli/v2/test_secrets.py">

<violation number="1" location="tests/units/reflex_cli/v2/test_secrets.py:89">
P1: These new caplog assertions will never capture the log records: the reflex logging pipeline sets propagate=False on the reflex_cli root logger in configure() (triggered by every command via console.set_log_level), so records on reflex_cli.v2.secrets don't reach the root logger where caplog attaches its handler. caplog.records will be empty and the tests fail. Capture at the reflex_cli logger instead (e.g. caplog.at_level / attach a handler to logging.getLogger('reflex_cli')) or assert on the rendered output.</violation>
</file>

<file name="packages/reflex-hosting-cli/pyproject.toml">

<violation number="1" location="packages/reflex-hosting-cli/pyproject.toml:21">
P2: The new `reflex-base >= 0.9.8.post19.dev0` dependency is an unpublishable `.dev` pin. The repo's publish gate (`uv run python scripts/check_min_deps.py --check-dev-pins`) fails for any package that declares a `*.dev` dependency pin, and this minimum will not be satisfiable from PyPI once reflex-hosting-cli is published (it only resolves locally through the added `[tool.uv.sources]` workspace entry). This is acknowledged as temporary in the PR description (re-pin at the 0.9.9 release), but it will block the hosting CLI publish gate in the meantime — worth tracking so it isn't merged/released with the dev pin still in place.</violation>
</file>

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

Re-trigger cubic</sub>