@11agents/cli 0.1.25 → 0.1.26

package/package.json

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

package/src/commands/runtime.js

@@ -1061,6 +1061,21 @@ function buildCodexPrompt(task) {
     '',
     'MCP tool guidance:',
     '- If the task needs image generation, use the hosted 11agents MCP `image_generate` tool when available.',
+    '- Recommended image_generate defaults: model="nano", nano_model="preview", aspect="1:1", image_size="2K".',
+    '- nano_model alternatives: "preview", "pro", "flash". Use "preview" for reliable default quality, "pro" for harder prompts, and "flash" for faster drafts.',
+    '- aspect alternatives: "1:1", "16:9", "9:16", "4:3", "3:4". Choose the closest ratio to the final placement.',
+    '- 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.',
+    '',
+    'Final task comment requirements:',
+    '> [!IMPORTANT]',
+    '> Default to a directly reviewable final comment. Do not only say the task is done.',
+    '- Every deliverable must appear in the final comment as a Markdown link to the file in agent_results_dir, for example `[final image](<absolute path>)` or `[report](<absolute path>)`.',
+    '- Put generated images, reports, datasets, and other final artifacts in agent_results_dir before linking them. The platform will upload allowed local links from agent_results_dir and replace them with reviewable asset URLs.',
+    '- Include a `## Deliverables` section first when files or generated media exist. Include a compact `## Review Notes` section after it with what changed and what to inspect.',
+    '- Use Markdown tables for comparisons, parameter lists, changelogs, data analysis, and multi-field entries.',
+    '- Use `##` and `###` headings, blank lines between paragraphs, bold keywords for important labels, and GitHub alert blocks for important notes or warnings.',
+    '- Use ordered lists for step-by-step workflows and unordered lists for parallel facts. Use fenced code blocks with a language tag, and use mermaid for flows or architecture when a diagram is useful.',
     '',
     'Task context:',
     compactJson({