reflex-dev/reflex

reflex-dev

reflex

Blog Docs Changelog

Performance History

Latest Results

fix(tokens): fail claim after exhausted NX retries Signed-off-by: Anas Khan <83116240+anxkhn@users.noreply.github.com>

anxkhn:fix/atomic-redis-token-claim

39 minutes ago

Fix flag ordering and reservation lifetime in the JSON stdout reservation Both from review on #6917. `json_requested` read argv as a set, so it disagreed with click wherever order mattered: click parses a boolean flag pair last-wins, and `--no-json --json` enables JSON while the set test answered "a refusal is present". Scanning back to front gives click's answer. The same disagreement came from combined short flags -- `-ij` is `-i -j` to click and was nothing to a membership test -- so the scan reads those too. Reading them means it can also fire on a `-j` click would take as another option's value, which is the direction to be wrong in: a message on stderr costs some context, one inside the document costs the whole parse. The reservation is process-global and nothing released it, so a `--json` command left every later log line in the process writing to stderr. A CLI process exits and never notices; an embedding one, or a second run in the same interpreter, does. It now follows the click context's lifetime and restores the previous value on close. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UqTVZN9bsCxt7hz5U3qJok

claude/eng-11018-a0edp7

14 hours ago

ENG-11018: make reflex_cli usable by an agent (--json, non-interactive, --follow) An agent delegating to `reflex cloud` had three ways to get stuck: it got human-formatted tables to regex, a prompt could block it forever, and `apps logs` followed by default and never returned. Every command in `reflex cloud` now takes `--json`. The document is written straight to stdout rather than through the console, and passing the flag reserves stdout for it: log records, tables, rules, spinners and progress bars render to stderr for the duration, so a warning from a helper deep in the call stack cannot land in the middle of the output. The reservation is also taken from argv in the group callback, because that callback speaks (the reflex-version warning) before click has parsed the subcommand's options. `--interactive` is now one shared option defaulting to whether stdout is a terminal, instead of thirty copies defaulting to True. A pipe, a CI job or an agent gets the non-interactive path it would have had to ask for; a person at a terminal sees no change. `apps logs --follow` defaults to off. Following means prompting between pages, and a prompt nobody answers is a command that never exits, so it is opt-in and is refused outright in JSON mode, where paging belongs to the caller. Commands that only logged their outcome now report it: a refusal comes back as `"deleted": false` with the server's message rather than as a success, and logs that could not be read stay distinguishable from an app with none. `generate_config` returns the path it wrote, so `config` no longer claims to have generated a file it declined to overwrite. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UqTVZN9bsCxt7hz5U3qJok

claude/eng-11018-a0edp7

15 hours ago

feat(log): deprecate the legacy console logging helpers (#6867) console.debug/info/success/log/warn/error/timing now emit a runtime deprecation warning (removal in 1.0) and are marked with typing_extensions.deprecated for type-level warnings. Behavior is otherwise unchanged; the interactive Rich features (print/rule/ status/ask/progress) remain first-class.

main

18 hours ago

ENG-10963 refactor(log): hosting CLI shares the reflex-base console and logging (4/5) (#6866) * refactor(log): hosting CLI shares the reflex-base console and logging 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. Debug output renders purple (was blue), errors go to stderr (was stdout), and success messages are hidden at --loglevel warning. The now-redundant LogLevel conversion mapper in reflex/reflex.py is removed. * chore(news): name the hosting CLI fragment after the PR --------- Co-authored-by: Claude <noreply@anthropic.com>

main

19 hours ago

feat(log): deprecate the legacy console logging helpers console.debug/info/success/log/warn/error/timing now emit a runtime deprecation warning (removal in 1.0) and are marked with typing_extensions.deprecated for type-level warnings. Behavior is otherwise unchanged; the interactive Rich features (print/rule/ status/ask/progress) remain first-class.

farhan/eng-10963-log-5-deprecate-console

19 hours ago

clarify that the headers-fallback leg reuses the state's current sid The sid in that payload equals the one the state already holds from the previous event, so the session compares equal and only the headers differ; name the sid and say so, since the literal reads like a second session change.

alek/router-delta-slim

19 hours ago

farhan/eng-10963-log-5-deprecate-console

19 hours ago

Latest Branches

+71%

fix(tokens): claim redis socket tokens atomically#6771

16 hours ago

bc6364e

anxkhn:fix/atomic-redis-token-claim

+73%

ENG-11018: Make the cloud CLI agent-usable (--json everywhere, non-interactive off a TTY, --follow opt-in)#6917

14 hours ago

8f690bb

claude/eng-11018-a0edp7

ENG-10963 feat(log): deprecate the legacy console logging helpers (5/5)#6867

10 days ago

90b1058

farhan/eng-10963-log-5-deprecate-console

Home Terms Privacy Docs