@11agents/cli 0.1.29 → 0.1.30

package/mobile-runtime/python/src/device_control/cli.py

@@ -983,7 +983,7 @@ def main() -> None:
                 topics=args.topics,
                 dry_run=args.dry_run,
                 confirm_no_disclosure_needed=args.confirm_no_disclosure_needed,
-                copy_link_after_publish=args.copy_link_after_publish,
+                copy_link_after_publish=args.copy_link_after_publish and not args.dry_run,
                 resume_post_form=args.resume_post_form,
             )
 
@@ -1174,8 +1174,16 @@ def _add_publish_xiaohongshu_args(parser: argparse.ArgumentParser) -> None:
     )
     parser.add_argument(
         "--copy-link-after-publish",
+        dest="copy_link_after_publish",
         action="store_true",
-        help="After a successful publish, open the share sheet, tap copy link, and try to read the copied URL.",
+        default=True,
+        help="After a successful publish, open the share sheet, tap copy link, and try to read the copied URL. Enabled by default for live publish.",
+    )
+    parser.add_argument(
+        "--no-copy-link-after-publish",
+        dest="copy_link_after_publish",
+        action="store_false",
+        help="Disable automatic Xiaohongshu link recovery after publish.",
     )
     parser.add_argument("--parallel", action="store_true", help="Run target devices concurrently. Hard-capped at 5.")
     parser.add_argument("--max-concurrency", type=int, default=MAX_PARALLEL_DEVICES, help="Max concurrent devices, 1-5.")

package/mobile-runtime/skills/android-group-control-cli/references/command-reference.md

@@ -84,7 +84,7 @@ X uses one `body` field, not a title/body split.
 11agents mobile copy-xiaohongshu-link --device D03 --record-id pub_123 --json --task-id TASK_123
 ```
 
-Use `--confirm-no-disclosure-needed` only when the approved package and policy explicitly allow it.
+Live Xiaohongshu publish recovers the note link by default after publish. Use `--no-copy-link-after-publish` only when automatic link recovery is explicitly not wanted. Use `--confirm-no-disclosure-needed` only when the approved package and policy explicitly allow it.
 
 ## Records And Data Recovery
 

package/mobile-runtime/skills/android-publish-xiaohongshu/SKILL.md

@@ -23,8 +23,8 @@ If approval, account lifecycle, media/package path, text fields, or device readi
 Image/video note:
 
 ```bash
-11agents mobile publish-xiaohongshu --device D03 --post-type image --image "/path/image.jpg" --title "title" --caption "body" --copy-link-after-publish --json --task-id TASK_123
-11agents mobile publish-xiaohongshu --device D03 --post-type video --video "/path/video.mp4" --title "title" --caption "body" --copy-link-after-publish --json --task-id TASK_123
+11agents mobile publish-xiaohongshu --device D03 --post-type image --image "/path/image.jpg" --title "title" --caption "body" --json --task-id TASK_123
+11agents mobile publish-xiaohongshu --device D03 --post-type video --video "/path/video.mp4" --title "title" --caption "body" --json --task-id TASK_123
 ```
 
 Structured package:
@@ -33,7 +33,7 @@ Structured package:
 11agents mobile publish-xiaohongshu --device D03 --publish-package "/path/publish_package.json" --json --task-id TASK_123
 ```
 
-Successful live publish is only confirmed after the CLI taps the final publish button, waits without tapping while Xiaohongshu shows upload/progress state, then opens the "我" page, opens the note whose title matches the expected title, and verifies the detail page against the expected title/body. If that evidence does not match, treat the result as `failed`; do not claim publish success from the publish button tap alone.
+Successful live publish is only confirmed after the CLI taps the final publish button, waits without tapping while Xiaohongshu shows upload/progress state, closes and relaunches Xiaohongshu, then opens the "我" page, opens the note whose title matches the expected title or the first visible profile note as a verified fallback, and verifies the detail page against the expected title/body. The CLI recovers the note link by default for live publish; use `--no-copy-link-after-publish` only when link recovery is explicitly not wanted. If that evidence does not match, treat the result as `failed`; do not claim publish success from the publish button tap alone.
 
 Link copy after publish or during the recovery skill:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@11agents/cli",
-  "version": "0.1.29",
+  "version": "0.1.30",
   "description": "11agents local runtime and telemetry CLI",
   "type": "module",
   "bin": {

package/src/commands/runtime.js

@@ -1083,13 +1083,12 @@ function buildCodexPrompt(task) {
     '- image_size alternatives: "1K", "2K". For a specific output size, pass aspect and image_size; pass size only when the MCP tool/provider explicitly supports the requested exact dimensions.',
     '- Use model="gpt" with model_id only when the task or current project notes confirm that GPT image generation is available for the hosted MCP key.',
     '- MCP authentication (agent_planning, database_sync, knowledge_sync, image_generate, etc.):',
-    '  1. Find your project_slug from the task context (task.workspace.slug).',
-    '  2. Open ~/.11agents/credentials.yaml and read the value under tokens.<project_slug>.',
-    '  3. Use that value as the Bearer token in the Authorization header for the 11agents hosted MCP endpoint.',
-    '  4. If the key is missing from credentials.yaml, add it:',
-    '       tokens:',
-    '         <project_slug>: <your-token>',
-    '     Get the token from the 11agents platform → open your project → Tokens menu.',
+    '  - The GTM_SWARM_TOKEN env var is already set to the correct project token for this workspace.',
+    '  - Configure the 11agents hosted MCP server using that env var:',
+    '      {"mcpServers":{"11agents-project-sync":{"url":"https://app.11agents.ai/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer $GTM_SWARM_TOKEN"}}}}',
+    '  - NEVER hardcode the token value — always reference $GTM_SWARM_TOKEN so the config stays correct across workspaces.',
+    '  - If GTM_SWARM_TOKEN is missing, get the token from ~/.11agents/credentials.yaml under tokens.<project_slug>.',
+    '    If that file is empty, go to the 11agents platform → your project → Tokens menu.',
     '',
     'Final task comment requirements:',
     '> [!IMPORTANT]',