@melaya/runner 1.0.93 → 1.0.94

package/dist/assistantHost.py

@@ -205,13 +205,19 @@ def _build_agent():
         "TikTok). Opening the wrong app is a FAILED task, not a reasonable default. "
         "After the user authorizes the app, phone_list_apps reflects it immediately — "
         "re-check and open the REQUESTED app.\n"
-        "- You are FULLY AUTONOMOUS on the phone: NEVER ask the user a question, "
-        "never end your turn asking for confirmation or offering a choice — make the "
-        "reasonable decision and DO it (the ONE exception is the EXACT-APP rule above: "
-        "a missing app is a stop, not a substitution). If a feed is algorithmic, use "
-        "the app's own Search / Explore to find the right content yourself. Keep going "
-        "until the task is COMPLETE (e.g. all N comments posted) or you are genuinely "
-        "blocked; only then report what you did and what (if anything) is blocked.\n"
+        "- You are AUTONOMOUS on the phone: for routine choices, make the reasonable "
+        "decision and DO it — never stall the run by ENDING YOUR TURN to ask in chat. "
+        "But when you hit a GENUINE fork you cannot reasonably resolve on your own (which "
+        "of several accounts to act as, a truly ambiguous target, a risky irreversible "
+        "step), or you want a go/no-go before continuing a long task, call "
+        "phone_ask_user(question): it expands the Melaya tile ON THE PHONE into a reply "
+        "card and BLOCKS for the user's typed answer WITHOUT ending your turn, so the run "
+        "continues seamlessly the moment they reply. Use it SPARINGLY, for real decisions "
+        "only — not routine ones. The EXACT-APP rule still holds (a missing app is a stop, "
+        "not a substitution). If a feed is algorithmic, use the app's own Search / Explore "
+        "to find the right content yourself. Keep going until the task is COMPLETE (e.g. "
+        "all N comments posted) or you are genuinely blocked; only then report what you "
+        "did and what (if anything) is blocked.\n"
         if phone_enabled else ""
     )
     connector_rule = (
@@ -246,13 +252,16 @@ def _build_agent():
         model_name=model,
         provider=provider,
         api_key="",  # model.py resolves the provider's own creds (OAuth off disk / localhost)
-        # Phone tasks are many-step (each comment ≈ screen_tree→tap→type→post), so
-        # give them room like the device template (40); read-only Q&A needs few.
-        # Connector WRITE tasks are equally many-step (e.g. "message all my recent
-        # LinkedIn connections" = 1 list + N sends, each its own reasoning+HITL
-        # round), so they need the same headroom — 8 hit the cap mid-task and
-        # forced _summarizing() on a half-finished tool batch.
-        max_iters=40 if (phone_enabled or connector_services) else 8,
+        # Phone tasks that act on N items ("like + comment on 10 posts") take
+        # ~10-15 tool calls EACH (screen_tree→read→tap→type→post_comment→verify→
+        # swipe to the next), so a flat 40 capped a 10-post run at ~3 done and
+        # forced a mid-task stop — which also ends the turn and tears down the
+        # phone working-overlay, snapping the phone back to the Melaya app before
+        # the task is finished. Give phone runs real headroom (they are HITL-gated,
+        # so each write still needs the user's tap — cost stays bounded). Connector
+        # WRITE fan-outs (1 list + N sends, each its own reasoning+HITL round) keep
+        # the 40 that fits them; read-only Q&A needs very few.
+        max_iters=100 if phone_enabled else (40 if connector_services else 8),
         reliability=True,
         bounded_memory=True,
     )

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@melaya/runner",
-  "version": "1.0.93",
+  "version": "1.0.94",
   "description": "Run Melaya AI pipelines locally with your own LM Studio or Ollama models",
   "license": "UNLICENSED",
   "private": false,