webbee 0.3.44__tar.gz → 0.3.46__tar.gz

{webbee-0.3.44 → webbee-0.3.46}/CHANGELOG.md

@@ -1,5 +1,45 @@
 # Changelog
 
+## 0.3.46
+
+Fixed a real jitter bug in text selection: dragging to select past the
+bottom (or top) of the visible output no longer makes the pane "jump
+around" instead of scrolling smoothly.
+
+- **Root cause:** a real terminal fires MOUSE_MOVE far more often than
+  once while the pointer sits at the viewport edge (every pixel of hand
+  tremor counts as a new event) -- and EVERY one of those was scrolling
+  the pane immediately, at the same time the dock's own ticker
+  (`edge_tick`) was ALSO scrolling the same pane every 0.25s to keep the
+  drag going while the mouse holds still. Two independent scroll sources
+  racing each other on the same viewport is exactly what looked like
+  "the window runs back and forth" while trying to select a big chunk of
+  text (Valentin, live 2026-07-31).
+- **Fix:** the immediate scroll now fires ONLY on the actual edge
+  transition (the moment the drag first reaches the edge); every
+  following MOUSE_MOVE at the same edge just keeps the selection armed
+  and leaves ALL the ongoing scrolling to the ticker's one steady 0.25s
+  cadence -- the exact same one-source-of-truth contract the queue/todo
+  panels and tab bar already use for their own edge-forwarded drags, now
+  applied consistently everywhere in the terminal so no two panes/panels
+  ever fight over the same scroll.
+
+## 0.3.45
+
+Consent prompts stop being an easy-to-miss detail:
+
+- **Both the kernel consent (`? approve ...`) and the local remote-control
+  yes/no ask now print as a bordered card, right in the conversation, the
+  moment they're asked** -- the same proven Panel this terminal already
+  uses for the billing and login prompts, so it reflows correctly to
+  whatever width the terminal actually has (a phone's SSH client, a narrow
+  tmux pane, a full window). The question and the "how to answer"
+  instructions (`y/yes -> do it`, `n/no -> skip it`, or type your own
+  reply) now live in the SAME box -- nothing to go hunting for in a
+  toolbar hint several rows away. The underlying protocol is unchanged:
+  still a bare raw string relayed verbatim for the kernel to interpret
+  (ICNLI, safe-by-default) -- this is a display-only change.
+
 ## 0.3.44
 
 Three real Home-dashboard bugs, found and fixed:

{webbee-0.3.44 → webbee-0.3.46}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: webbee
-Version: 0.3.44
+Version: 0.3.46
 Summary: Webbee 🐝 — the Imperal Cloud coding agent in your terminal
 Project-URL: Homepage, https://imperal.io
 Project-URL: Documentation, https://docs.imperal.io

{webbee-0.3.44 → webbee-0.3.46}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "webbee"
-version = "0.3.44"
+version = "0.3.46"
 description = "Webbee 🐝 — the Imperal Cloud coding agent in your terminal"
 readme = "README.md"
 license = "MIT"

webbee-0.3.46/src/webbee/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.3.46"

{webbee-0.3.44 → webbee-0.3.46}/src/webbee/render.py

@@ -614,12 +614,38 @@ class RichSink:
         NEVER interpret (the kernel decides, ICNLI). When the dock is running
         the reply comes through the pinned box via an asyncio.Future (no
         blocking input on the event loop); otherwise fall back to the injected
-        sync reader (tests / non-tty)."""
+        sync reader (tests / non-tty).
+
+        webbee-code-consent-card-v1: this used to be one dim, easy-to-miss
+        line in the feed plus a SEPARATE hint buried in the toolbar below --
+        several users said it wasn't obvious what was even being asked, let
+        alone how to answer it. Now it's a bordered card printed RIGHT IN
+        THE CONVERSATION, at the moment it's asked -- same proven Panel this
+        module already uses for the billing/login prompts, so it reflows to
+        whatever width the terminal actually has (phone SSH client, a narrow
+        tmux pane, a full-width window -- all get a readable card, not a
+        clipped line). The question AND the "how to answer" instructions
+        live in the SAME box, so there's nothing to hunt for elsewhere on
+        screen. The protocol contract is unchanged: still a bare raw string
+        relayed verbatim for the kernel to interpret (ICNLI, safe-by-default)."""
         label = _clean(f"{app_id}·{tool}" if app_id else tool)
-        sal = _clean(_salient_arg(args))
-        w = self.console.width
-        self.console.print(Text.assemble(("  ? approve ", "yellow"), (label, "dim"),
-                                          (("  " + sal[:trunc(w, 0.4, 60)]) if sal else "", "dim")))
+        sal = _clean(_salient_arg(args))[:500]
+        body = Text()
+        body.append(label, style=f"bold {_ACCENT}")
+        if sal:
+            body.append("\n" + sal, style="white")
+        body.append("\n\n")
+        body.append("y", style="bold green")
+        body.append(" / ", style="dim")
+        body.append("yes", style="bold green")
+        body.append("  →  do it     ", style="dim")
+        body.append("n", style="bold red")
+        body.append(" / ", style="dim")
+        body.append("no", style="bold red")
+        body.append("  →  skip it\n", style="dim")
+        body.append("or just type your own reply in any language — Enter to send", style="dim")
+        self.console.print(_pad(Panel(body, title="🔐 wants to do this — approve?",
+                                      border_style=_BEE)))
         fut = self._arm_consent(label, sal)
         if fut is None:                       # non-tty / no running app
             raw = self._input("     ")
@@ -643,8 +669,26 @@ class RichSink:
         all return False, so the caller keeps the current mode. This is a
         LOCAL policy decision, not a kernel consent, so the reply is
         interpreted here rather than relayed (ICNLI raw-relay applies to
-        kernel consents only)."""
-        self.console.print(_pad(Text("⚠ " + _clean(question), style=f"bold {_BEE}")))
+        kernel consents only).
+
+        webbee-code-consent-card-v1: same bordered-card treatment as
+        ask_consent -- a bare "⚠ ..." line was just as easy to miss as the
+        old one-line kernel consent was. The card reflows to the terminal's
+        real width on any device, and states the y/n instructions right
+        where the question is instead of leaving them implicit."""
+        body = Text()
+        body.append(_clean(question), style=f"bold {_BEE}")
+        body.append("\n\n")
+        body.append("y", style="bold green")
+        body.append(" / ", style="dim")
+        body.append("yes", style="bold green")
+        body.append("  →  allow     ", style="dim")
+        body.append("n", style="bold red")
+        body.append(" / ", style="dim")
+        body.append("no", style="bold red")
+        body.append("  →  stay as-is (default)", style="dim")
+        self.console.print(_pad(Panel(body, title="⚠ another surface is asking",
+                                      border_style=_BEE)))
         fut = self._arm_consent(question, question)
         try:
             if fut is None:                    # non-tty / no dock → sync reader

{webbee-0.3.44 → webbee-0.3.46}/src/webbee/selection.py

@@ -87,11 +87,29 @@ def make_select_control(pane, FormattedTextControl, MouseEventType, MouseButton)
                     return NotImplemented
                 pane._edge_ticks = 0                # a fresh MOUSE_MOVE means the pointer isn't parked
                 y = ev.position.y
+                # webbee-code-selection-scroll-jitter-v1: a REAL terminal fires
+                # MOUSE_MOVE far more often than once (every pixel of hand
+                # tremor while parked at the edge trying to select further) --
+                # scrolling immediately on EVERY one of those, on top of
+                # edge_tick() ALREADY scrolling the same pane every 0.25s once
+                # armed, stacked two independent scroll sources racing each
+                # other and made the viewport visibly jump/jitter instead of
+                # scrolling smoothly (Valentin, live 2026-07-31: "окно бегает
+                # туда сюда"). The immediate nudge now fires ONLY on the edge
+                # transition (armed 0 -> 1/-1) for snappy first-touch
+                # feedback; every following MOUSE_MOVE that's STILL at the
+                # same edge just re-affirms the arm (resets _edge_ticks above,
+                # so the runaway guard doesn't fire) and leaves the ONGOING
+                # scroll entirely to edge_tick()'s single steady cadence --
+                # exactly the contract forward_mouse() already uses for the
+                # neighbor panels.
                 if y >= pane._view_h - 1:
-                    pane.scroll(3)
+                    if pane._edge_drag != 1:
+                        pane.scroll(3)
                     pane._edge_drag = 1
                 elif y <= 0:
-                    pane.scroll(-3)
+                    if pane._edge_drag != -1:
+                        pane.scroll(-3)
                     pane._edge_drag = -1
                 else:
                     pane._edge_drag = 0

{webbee-0.3.44 → webbee-0.3.46}/tests/test_render.py

@@ -299,6 +299,49 @@ def test_consent_shows_human_summary_not_dict():
     assert "notes·delete_note" in out
 
 
+# ── webbee-code-consent-card-v1: the consent card is a real, hard-to-miss
+# bordered block printed IN the conversation, with the y/n instructions
+# living right next to the question -- not a dim one-liner + a separate
+# toolbar hint the user has to go hunting for. ────────────────────────────
+
+def test_consent_is_a_bordered_card_with_inline_instructions():
+    console = Console(record=True, width=90)
+    s = RichSink(console=console, live_enabled=False,
+                 input_fn=lambda p: "yes", clock=lambda: 0.0)
+    asyncio.run(s.ask_consent("notes", "delete_note", {"title": "Q3 budget"}))
+    out = console.export_text()
+    # a real Panel border, not a bare printed line
+    assert "\u256d" in out or "\u2500" in out   # rounded-corner or horizontal rule glyph
+    assert "approve?" in out
+    # the how-to-answer instructions are IN the card, not somewhere else
+    assert "yes" in out and "no" in out
+    assert "do it" in out and "skip it" in out
+    assert "notes·delete_note" in out
+
+
+def test_consent_card_reflows_to_narrow_terminal_width():
+    # A phone SSH client / narrow tmux pane: the card must not crash or
+    # silently drop the question -- Panel reflows, same as billing/login.
+    console = Console(record=True, width=28)
+    s = RichSink(console=console, live_enabled=False,
+                 input_fn=lambda p: "y", clock=lambda: 0.0)
+    asyncio.run(s.ask_consent("mail", "delete", {"query": "old newsletters"}))
+    out = console.export_text()
+    assert "mail" in out and "delete" in out
+    assert "yes" in out and "no" in out
+
+
+def test_ask_yes_no_is_also_a_bordered_card_with_instructions():
+    console = Console(record=True, width=90)
+    s = RichSink(console=console, live_enabled=False,
+                 input_fn=lambda p: "y", clock=lambda: 0.0)
+    asyncio.run(s.ask_yes_no("switch to autopilot — allow? [y/n]"))
+    out = console.export_text()
+    assert "\u256d" in out or "\u2500" in out
+    assert "allow" in out.lower()
+    assert "yes" in out and "no" in out
+
+
 def test_user_echo_is_unboxed_line():
     s = _sink()
     s.user_echo("delete my Q3 note")

{webbee-0.3.44 → webbee-0.3.46}/tests/test_tui.py

@@ -258,6 +258,42 @@ def test_drag_at_bottom_edge_scrolls_and_grows_selection():
     assert pane._edge_drag == 0
 
 
+def test_repeated_mouse_move_at_same_edge_does_not_double_scroll():
+    # webbee-code-selection-scroll-jitter-v1: a real terminal fires MOUSE_MOVE
+    # repeatedly while the pointer sits at the SAME edge (hand tremor) --
+    # only the FIRST one (the 0 -> armed transition) may scroll immediately;
+    # every following MOUSE_MOVE at the same edge must leave the offset
+    # alone (still armed, still selecting) and let edge_tick() do the only
+    # ongoing scrolling, one steady source instead of two racing.
+    from prompt_toolkit.data_structures import Point
+    from prompt_toolkit.mouse_events import MouseButton, MouseEvent, MouseEventType
+
+    from webbee.tui import OutputPane
+
+    pane = OutputPane(width=80)
+    pane._view_h = 10
+    pane._io.write("\n".join(f"line{i}" for i in range(100)))
+    pane._offset = 0
+
+    down = MouseEvent(position=Point(0, 5), event_type=MouseEventType.MOUSE_DOWN,
+                      button=MouseButton.LEFT, modifiers=frozenset())
+    pane.control.mouse_handler(down)
+
+    move = MouseEvent(position=Point(3, 9), event_type=MouseEventType.MOUSE_MOVE,
+                      button=MouseButton.LEFT, modifiers=frozenset())
+    pane.control.mouse_handler(move)
+    assert pane._offset == 3 and pane._edge_drag == 1   # first touch: one immediate nudge
+
+    # the pointer trembles but stays at the SAME bottom row -- must NOT scroll again.
+    pane.control.mouse_handler(move)
+    pane.control.mouse_handler(move)
+    assert pane._offset == 3 and pane._edge_drag == 1   # unchanged -- no double scroll
+
+    # only edge_tick() advances it further, at its own steady cadence.
+    pane.edge_tick()
+    assert pane._offset == 6
+
+
 def test_edge_drag_resets_on_mouse_up_and_top_edge_mirrors():
     from prompt_toolkit.data_structures import Point
     from prompt_toolkit.mouse_events import MouseButton, MouseEvent, MouseEventType

webbee-0.3.44/src/webbee/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.3.44"