@melaya/runner 1.1.24 → 1.1.25
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/assistantHost.py +14 -6
- package/package.json +1 -1
package/dist/assistantHost.py
CHANGED
|
@@ -719,12 +719,20 @@ def _build_agent():
|
|
|
719
719
|
max_iters=(int(os.environ.get("MEL_ASSISTANT_MAX_ITERS_PHONE", "300") or "300") if phone_enabled
|
|
720
720
|
else (int(os.environ.get("MEL_ASSISTANT_MAX_ITERS_BROWSER", "300") or "300") if browser_enabled
|
|
721
721
|
else (40 if connector_services else 8))),
|
|
722
|
-
#
|
|
723
|
-
#
|
|
724
|
-
#
|
|
725
|
-
#
|
|
726
|
-
#
|
|
727
|
-
|
|
722
|
+
# EVERY assistant turn is long-horizon, not only device-driving ones.
|
|
723
|
+
#
|
|
724
|
+
# The codex cap is a latency default written for pipeline phases. An
|
|
725
|
+
# assistant turn is interactive - a human is waiting - and its shape is
|
|
726
|
+
# always read, do one thing, read again. A connector turn alone needs
|
|
727
|
+
# search_tools + activate_tool + the call + a synthesis round: already
|
|
728
|
+
# four, so a cap of three truncates before the model can answer.
|
|
729
|
+
#
|
|
730
|
+
# This was briefly gated on (phone or browser). That passed testing only
|
|
731
|
+
# because the tester's runner advertises browser capability, and
|
|
732
|
+
# _browser_capable() is CAPABILITY presence rather than turn usage - so
|
|
733
|
+
# it was true for all of their turns. A user whose runner is not
|
|
734
|
+
# browser-capable would still have been clamped to 3 on ordinary chat.
|
|
735
|
+
long_horizon=True,
|
|
728
736
|
reliability=True,
|
|
729
737
|
bounded_memory=True,
|
|
730
738
|
)
|