@within-7/minto 0.3.9 → 0.4.0

package/dist/constants/modelCapabilities.js.map

@@ -1,7 +1,7 @@
 {
   "version": 3,
   "sources": ["../../src/constants/modelCapabilities.ts"],
-  "sourcesContent": ["import { ModelCapabilities } from '@minto-types/modelCapabilities'\n\n// GPT-5 standard capability definition\nconst GPT5_CAPABILITIES: ModelCapabilities = {\n  apiArchitecture: {\n    primary: 'responses_api',\n    fallback: 'chat_completions',\n  },\n  parameters: {\n    maxTokensField: 'max_completion_tokens',\n    supportsReasoningEffort: true,\n    supportsVerbosity: true,\n    temperatureMode: 'fixed_one',\n  },\n  toolCalling: {\n    mode: 'custom_tools',\n    supportsFreeform: true,\n    supportsAllowedTools: true,\n    supportsParallelCalls: true,\n  },\n  stateManagement: {\n    supportsResponseId: true,\n    supportsConversationChaining: true,\n    supportsPreviousResponseId: true,\n  },\n  streaming: {\n    supported: false, // Responses API doesn't support streaming yet\n    includesUsage: true,\n  },\n}\n\n// Chat Completions standard capability definition\nconst CHAT_COMPLETIONS_CAPABILITIES: ModelCapabilities = {\n  apiArchitecture: {\n    primary: 'chat_completions',\n  },\n  parameters: {\n    maxTokensField: 'max_tokens',\n    supportsReasoningEffort: false,\n    supportsVerbosity: false,\n    temperatureMode: 'flexible',\n  },\n  toolCalling: {\n    mode: 'function_calling',\n    supportsFreeform: false,\n    supportsAllowedTools: false,\n    supportsParallelCalls: true,\n  },\n  stateManagement: {\n    supportsResponseId: false,\n    supportsConversationChaining: false,\n    supportsPreviousResponseId: false,\n  },\n  streaming: {\n    supported: true,\n    includesUsage: true,\n  },\n}\n\n// Complete model capability mapping table\nexport const MODEL_CAPABILITIES_REGISTRY: Record<string, ModelCapabilities> = {\n  // GPT-5 series\n  'gpt-5': GPT5_CAPABILITIES,\n  'gpt-5-mini': GPT5_CAPABILITIES,\n  'gpt-5-nano': GPT5_CAPABILITIES,\n  'gpt-5-chat-latest': GPT5_CAPABILITIES,\n\n  // GPT-4 series\n  'gpt-4o': CHAT_COMPLETIONS_CAPABILITIES,\n  'gpt-4o-mini': CHAT_COMPLETIONS_CAPABILITIES,\n  'gpt-4-turbo': CHAT_COMPLETIONS_CAPABILITIES,\n  'gpt-4': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // Claude series (supported through conversion layer)\n  'claude-3-5-sonnet-20241022': CHAT_COMPLETIONS_CAPABILITIES,\n  'claude-3-5-haiku-20241022': CHAT_COMPLETIONS_CAPABILITIES,\n  'claude-3-opus-20240229': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // O1 series (special reasoning models)\n  o1: {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      maxTokensField: 'max_completion_tokens',\n      temperatureMode: 'fixed_one',\n    },\n  },\n  'o1-mini': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      maxTokensField: 'max_completion_tokens',\n      temperatureMode: 'fixed_one',\n    },\n  },\n  'o1-preview': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      maxTokensField: 'max_completion_tokens',\n      temperatureMode: 'fixed_one',\n    },\n  },\n}\n\n// Intelligently infer capabilities for unregistered models\nexport function inferModelCapabilities(\n  modelName: string,\n): ModelCapabilities | null {\n  if (!modelName) return null\n\n  const lowerName = modelName.toLowerCase()\n\n  // GPT-5 series\n  if (lowerName.includes('gpt-5') || lowerName.includes('gpt5')) {\n    return GPT5_CAPABILITIES\n  }\n\n  // GPT-6 series (reserved for future)\n  if (lowerName.includes('gpt-6') || lowerName.includes('gpt6')) {\n    return {\n      ...GPT5_CAPABILITIES,\n      streaming: { supported: true, includesUsage: true },\n    }\n  }\n\n  // GLM series\n  if (lowerName.includes('glm-5') || lowerName.includes('glm5')) {\n    return {\n      ...GPT5_CAPABILITIES,\n      toolCalling: {\n        ...GPT5_CAPABILITIES.toolCalling,\n        supportsAllowedTools: false, // GLM might not support this\n      },\n    }\n  }\n\n  // O1 series\n  if (lowerName.startsWith('o1') || lowerName.includes('o1-')) {\n    return {\n      ...CHAT_COMPLETIONS_CAPABILITIES,\n      parameters: {\n        ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n        maxTokensField: 'max_completion_tokens',\n        temperatureMode: 'fixed_one',\n      },\n    }\n  }\n\n  // Default to null, let system use default behavior\n  return null\n}\n\n// Get model capabilities (with caching)\nconst capabilityCache = new Map<string, ModelCapabilities>()\n\nexport function getModelCapabilities(modelName: string): ModelCapabilities {\n  // Check cache\n  if (capabilityCache.has(modelName)) {\n    return capabilityCache.get(modelName)!\n  }\n\n  // Look up in registry\n  if (MODEL_CAPABILITIES_REGISTRY[modelName]) {\n    const capabilities = MODEL_CAPABILITIES_REGISTRY[modelName]\n    capabilityCache.set(modelName, capabilities)\n    return capabilities\n  }\n\n  // Try to infer\n  const inferred = inferModelCapabilities(modelName)\n  if (inferred) {\n    capabilityCache.set(modelName, inferred)\n    return inferred\n  }\n\n  // Default to Chat Completions\n  const defaultCapabilities = CHAT_COMPLETIONS_CAPABILITIES\n  capabilityCache.set(modelName, defaultCapabilities)\n  return defaultCapabilities\n}\n"],
-  "mappings": "AAGA,MAAM,oBAAuC;AAAA,EAC3C,iBAAiB;AAAA,IACf,SAAS;AAAA,IACT,UAAU;AAAA,EACZ;AAAA,EACA,YAAY;AAAA,IACV,gBAAgB;AAAA,IAChB,yBAAyB;AAAA,IACzB,mBAAmB;AAAA,IACnB,iBAAiB;AAAA,EACnB;AAAA,EACA,aAAa;AAAA,IACX,MAAM;AAAA,IACN,kBAAkB;AAAA,IAClB,sBAAsB;AAAA,IACtB,uBAAuB;AAAA,EACzB;AAAA,EACA,iBAAiB;AAAA,IACf,oBAAoB;AAAA,IACpB,8BAA8B;AAAA,IAC9B,4BAA4B;AAAA,EAC9B;AAAA,EACA,WAAW;AAAA,IACT,WAAW;AAAA;AAAA,IACX,eAAe;AAAA,EACjB;AACF;AAGA,MAAM,gCAAmD;AAAA,EACvD,iBAAiB;AAAA,IACf,SAAS;AAAA,EACX;AAAA,EACA,YAAY;AAAA,IACV,gBAAgB;AAAA,IAChB,yBAAyB;AAAA,IACzB,mBAAmB;AAAA,IACnB,iBAAiB;AAAA,EACnB;AAAA,EACA,aAAa;AAAA,IACX,MAAM;AAAA,IACN,kBAAkB;AAAA,IAClB,sBAAsB;AAAA,IACtB,uBAAuB;AAAA,EACzB;AAAA,EACA,iBAAiB;AAAA,IACf,oBAAoB;AAAA,IACpB,8BAA8B;AAAA,IAC9B,4BAA4B;AAAA,EAC9B;AAAA,EACA,WAAW;AAAA,IACT,WAAW;AAAA,IACX,eAAe;AAAA,EACjB;AACF;AAGO,MAAM,8BAAiE;AAAA;AAAA,EAE5E,SAAS;AAAA,EACT,cAAc;AAAA,EACd,cAAc;AAAA,EACd,qBAAqB;AAAA;AAAA,EAGrB,UAAU;AAAA,EACV,eAAe;AAAA,EACf,eAAe;AAAA,EACf,SAAS;AAAA;AAAA,EAGT,8BAA8B;AAAA,EAC9B,6BAA6B;AAAA,EAC7B,0BAA0B;AAAA;AAAA,EAG1B,IAAI;AAAA,IACF,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,gBAAgB;AAAA,MAChB,iBAAiB;AAAA,IACnB;AAAA,EACF;AAAA,EACA,WAAW;AAAA,IACT,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,gBAAgB;AAAA,MAChB,iBAAiB;AAAA,IACnB;AAAA,EACF;AAAA,EACA,cAAc;AAAA,IACZ,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,gBAAgB;AAAA,MAChB,iBAAiB;AAAA,IACnB;AAAA,EACF;AACF;AAGO,SAAS,uBACd,WAC0B;AAC1B,MAAI,CAAC,UAAW,QAAO;AAEvB,QAAM,YAAY,UAAU,YAAY;AAGxC,MAAI,UAAU,SAAS,OAAO,KAAK,UAAU,SAAS,MAAM,GAAG;AAC7D,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,OAAO,KAAK,UAAU,SAAS,MAAM,GAAG;AAC7D,WAAO;AAAA,MACL,GAAG;AAAA,MACH,WAAW,EAAE,WAAW,MAAM,eAAe,KAAK;AAAA,IACpD;AAAA,EACF;AAGA,MAAI,UAAU,SAAS,OAAO,KAAK,UAAU,SAAS,MAAM,GAAG;AAC7D,WAAO;AAAA,MACL,GAAG;AAAA,MACH,aAAa;AAAA,QACX,GAAG,kBAAkB;AAAA,QACrB,sBAAsB;AAAA;AAAA,MACxB;AAAA,IACF;AAAA,EACF;AAGA,MAAI,UAAU,WAAW,IAAI,KAAK,UAAU,SAAS,KAAK,GAAG;AAC3D,WAAO;AAAA,MACL,GAAG;AAAA,MACH,YAAY;AAAA,QACV,GAAG,8BAA8B;AAAA,QACjC,gBAAgB;AAAA,QAChB,iBAAiB;AAAA,MACnB;AAAA,IACF;AAAA,EACF;AAGA,SAAO;AACT;AAGA,MAAM,kBAAkB,oBAAI,IAA+B;AAEpD,SAAS,qBAAqB,WAAsC;AAEzE,MAAI,gBAAgB,IAAI,SAAS,GAAG;AAClC,WAAO,gBAAgB,IAAI,SAAS;AAAA,EACtC;AAGA,MAAI,4BAA4B,SAAS,GAAG;AAC1C,UAAM,eAAe,4BAA4B,SAAS;AAC1D,oBAAgB,IAAI,WAAW,YAAY;AAC3C,WAAO;AAAA,EACT;AAGA,QAAM,WAAW,uBAAuB,SAAS;AACjD,MAAI,UAAU;AACZ,oBAAgB,IAAI,WAAW,QAAQ;AACvC,WAAO;AAAA,EACT;AAGA,QAAM,sBAAsB;AAC5B,kBAAgB,IAAI,WAAW,mBAAmB;AAClD,SAAO;AACT;",
+  "sourcesContent": ["import { ModelCapabilities } from '@minto-types/modelCapabilities'\n\n// GPT-5 standard capability definition\nconst GPT5_CAPABILITIES: ModelCapabilities = {\n  apiArchitecture: {\n    primary: 'responses_api',\n    fallback: 'chat_completions',\n  },\n  parameters: {\n    maxTokensField: 'max_output_tokens',\n    supportsReasoningEffort: true,\n    supportsVerbosity: true,\n    temperatureMode: 'fixed_one',\n  },\n  toolCalling: {\n    mode: 'custom_tools',\n    supportsFreeform: true,\n    supportsAllowedTools: true,\n    supportsParallelCalls: true,\n  },\n  stateManagement: {\n    supportsResponseId: true,\n    supportsConversationChaining: true,\n    supportsPreviousResponseId: true,\n  },\n  streaming: {\n    supported: false, // Responses API doesn't support streaming yet\n    includesUsage: true,\n  },\n}\n\n// Chat Completions standard capability definition\nconst CHAT_COMPLETIONS_CAPABILITIES: ModelCapabilities = {\n  apiArchitecture: {\n    primary: 'chat_completions',\n  },\n  parameters: {\n    maxTokensField: 'max_tokens',\n    supportsReasoningEffort: false,\n    supportsVerbosity: false,\n    temperatureMode: 'flexible',\n  },\n  toolCalling: {\n    mode: 'function_calling',\n    supportsFreeform: false,\n    supportsAllowedTools: false,\n    supportsParallelCalls: true,\n  },\n  stateManagement: {\n    supportsResponseId: false,\n    supportsConversationChaining: false,\n    supportsPreviousResponseId: false,\n  },\n  streaming: {\n    supported: true,\n    includesUsage: true,\n  },\n}\n\n// OpenAI reasoning model capabilities (o1, o3, o4-mini)\nconst OPENAI_REASONING_CAPABILITIES: ModelCapabilities = {\n  ...CHAT_COMPLETIONS_CAPABILITIES,\n  parameters: {\n    ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n    maxTokensField: 'max_completion_tokens',\n    temperatureMode: 'fixed_one',\n  },\n}\n\n// OpenAI reasoning model with reasoning_effort support (o3, o4-mini)\nconst OPENAI_REASONING_WITH_EFFORT: ModelCapabilities = {\n  ...OPENAI_REASONING_CAPABILITIES,\n  parameters: {\n    ...OPENAI_REASONING_CAPABILITIES.parameters,\n    supportsReasoningEffort: true,\n  },\n}\n\n// Complete model capability mapping table\nexport const MODEL_CAPABILITIES_REGISTRY: Record<string, ModelCapabilities> = {\n  // GPT-5 series\n  'gpt-5': GPT5_CAPABILITIES,\n  'gpt-5-mini': GPT5_CAPABILITIES,\n  'gpt-5-nano': GPT5_CAPABILITIES,\n  'gpt-5-chat-latest': GPT5_CAPABILITIES,\n\n  // GPT-4 series\n  'gpt-4o': CHAT_COMPLETIONS_CAPABILITIES,\n  'gpt-4o-mini': CHAT_COMPLETIONS_CAPABILITIES,\n  'gpt-4-turbo': CHAT_COMPLETIONS_CAPABILITIES,\n  'gpt-4': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // Claude series (supported through conversion layer)\n  'claude-3-5-sonnet-20241022': CHAT_COMPLETIONS_CAPABILITIES,\n  'claude-3-5-haiku-20241022': CHAT_COMPLETIONS_CAPABILITIES,\n  'claude-3-opus-20240229': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // O1 series (reasoning models - no system messages, temperature omit)\n  o1: OPENAI_REASONING_CAPABILITIES,\n  'o1-mini': OPENAI_REASONING_CAPABILITIES,\n  'o1-preview': OPENAI_REASONING_CAPABILITIES,\n\n  // O3 series (reasoning models with reasoning_effort support)\n  'o3-mini': OPENAI_REASONING_WITH_EFFORT,\n  o3: OPENAI_REASONING_WITH_EFFORT,\n\n  // O4 series\n  'o4-mini': OPENAI_REASONING_WITH_EFFORT,\n\n  // Gemini series\n  'gemini-2.0-flash': CHAT_COMPLETIONS_CAPABILITIES,\n  'gemini-2.0-flash-lite': CHAT_COMPLETIONS_CAPABILITIES,\n  'gemini-2.5-pro': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      supportsReasoningEffort: true,\n    },\n  },\n  'gemini-2.5-flash': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      supportsReasoningEffort: true,\n    },\n  },\n\n  // DeepSeek series\n  'deepseek-chat': CHAT_COMPLETIONS_CAPABILITIES,\n  'deepseek-reasoner': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      temperatureMode: 'fixed_one',\n    },\n  },\n\n  // Mistral series\n  'mistral-large-latest': CHAT_COMPLETIONS_CAPABILITIES,\n  'mistral-small-latest': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // Grok (xAI) series\n  'grok-3': CHAT_COMPLETIONS_CAPABILITIES,\n  'grok-3-mini': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      supportsReasoningEffort: true,\n    },\n  },\n  'grok-2': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // Qwen series\n  'qwen-max': CHAT_COMPLETIONS_CAPABILITIES,\n  'qwen-plus': CHAT_COMPLETIONS_CAPABILITIES,\n  'qwen-turbo': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // GLM series (limited tool_choice, max 1 stop sequence)\n  'glm-4': CHAT_COMPLETIONS_CAPABILITIES,\n  'glm-4-plus': CHAT_COMPLETIONS_CAPABILITIES,\n\n  // Kimi reasoning series (temperature fixed at 1)\n  'kimi-k2': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      temperatureMode: 'fixed_one',\n    },\n  },\n  'kimi-k2.5': {\n    ...CHAT_COMPLETIONS_CAPABILITIES,\n    parameters: {\n      ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n      temperatureMode: 'fixed_one',\n    },\n  },\n}\n\n// Intelligently infer capabilities for unregistered models\nexport function inferModelCapabilities(\n  modelName: string,\n): ModelCapabilities | null {\n  if (!modelName) return null\n\n  const lowerName = modelName.toLowerCase()\n\n  // GPT-5 series\n  if (lowerName.includes('gpt-5') || lowerName.includes('gpt5')) {\n    return GPT5_CAPABILITIES\n  }\n\n  // GPT-6 series (reserved for future)\n  if (lowerName.includes('gpt-6') || lowerName.includes('gpt6')) {\n    return {\n      ...GPT5_CAPABILITIES,\n      streaming: { supported: true, includesUsage: true },\n    }\n  }\n\n  // O3 series (reasoning with effort)\n  if (lowerName.startsWith('o3') || lowerName.includes('o3-')) {\n    return OPENAI_REASONING_WITH_EFFORT\n  }\n\n  // O4 series (reasoning with effort)\n  if (lowerName.startsWith('o4') || lowerName.includes('o4-')) {\n    return OPENAI_REASONING_WITH_EFFORT\n  }\n\n  // O1 series (reasoning without effort)\n  if (lowerName.startsWith('o1') || lowerName.includes('o1-')) {\n    return OPENAI_REASONING_CAPABILITIES\n  }\n\n  // GLM series\n  if (lowerName.includes('glm')) {\n    return CHAT_COMPLETIONS_CAPABILITIES\n  }\n\n  // Gemini series\n  if (lowerName.includes('gemini')) {\n    return CHAT_COMPLETIONS_CAPABILITIES\n  }\n\n  // DeepSeek series\n  if (lowerName.includes('deepseek')) {\n    if (lowerName.includes('reasoner')) {\n      return {\n        ...CHAT_COMPLETIONS_CAPABILITIES,\n        parameters: {\n          ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n          temperatureMode: 'fixed_one',\n        },\n      }\n    }\n    return CHAT_COMPLETIONS_CAPABILITIES\n  }\n\n  // Mistral series\n  if (lowerName.includes('mistral')) {\n    return CHAT_COMPLETIONS_CAPABILITIES\n  }\n\n  // Grok series\n  if (lowerName.includes('grok')) {\n    return CHAT_COMPLETIONS_CAPABILITIES\n  }\n\n  // Qwen series\n  if (lowerName.includes('qwen')) {\n    return CHAT_COMPLETIONS_CAPABILITIES\n  }\n\n  // Kimi reasoning series (kimi-k2, kimi-k2.5, etc.)\n  if (lowerName.includes('kimi-k')) {\n    return {\n      ...CHAT_COMPLETIONS_CAPABILITIES,\n      parameters: {\n        ...CHAT_COMPLETIONS_CAPABILITIES.parameters,\n        temperatureMode: 'fixed_one',\n      },\n    }\n  }\n\n  // Default to null, let system use default behavior\n  return null\n}\n\n// Get model capabilities (with caching)\nconst capabilityCache = new Map<string, ModelCapabilities>()\n\nexport function getModelCapabilities(modelName: string): ModelCapabilities {\n  // Check cache\n  if (capabilityCache.has(modelName)) {\n    return capabilityCache.get(modelName)!\n  }\n\n  // Look up in registry\n  if (MODEL_CAPABILITIES_REGISTRY[modelName]) {\n    const capabilities = MODEL_CAPABILITIES_REGISTRY[modelName]\n    capabilityCache.set(modelName, capabilities)\n    return capabilities\n  }\n\n  // Try to infer\n  const inferred = inferModelCapabilities(modelName)\n  if (inferred) {\n    capabilityCache.set(modelName, inferred)\n    return inferred\n  }\n\n  // Default to Chat Completions\n  const defaultCapabilities = CHAT_COMPLETIONS_CAPABILITIES\n  capabilityCache.set(modelName, defaultCapabilities)\n  return defaultCapabilities\n}\n"],
+  "mappings": "AAGA,MAAM,oBAAuC;AAAA,EAC3C,iBAAiB;AAAA,IACf,SAAS;AAAA,IACT,UAAU;AAAA,EACZ;AAAA,EACA,YAAY;AAAA,IACV,gBAAgB;AAAA,IAChB,yBAAyB;AAAA,IACzB,mBAAmB;AAAA,IACnB,iBAAiB;AAAA,EACnB;AAAA,EACA,aAAa;AAAA,IACX,MAAM;AAAA,IACN,kBAAkB;AAAA,IAClB,sBAAsB;AAAA,IACtB,uBAAuB;AAAA,EACzB;AAAA,EACA,iBAAiB;AAAA,IACf,oBAAoB;AAAA,IACpB,8BAA8B;AAAA,IAC9B,4BAA4B;AAAA,EAC9B;AAAA,EACA,WAAW;AAAA,IACT,WAAW;AAAA;AAAA,IACX,eAAe;AAAA,EACjB;AACF;AAGA,MAAM,gCAAmD;AAAA,EACvD,iBAAiB;AAAA,IACf,SAAS;AAAA,EACX;AAAA,EACA,YAAY;AAAA,IACV,gBAAgB;AAAA,IAChB,yBAAyB;AAAA,IACzB,mBAAmB;AAAA,IACnB,iBAAiB;AAAA,EACnB;AAAA,EACA,aAAa;AAAA,IACX,MAAM;AAAA,IACN,kBAAkB;AAAA,IAClB,sBAAsB;AAAA,IACtB,uBAAuB;AAAA,EACzB;AAAA,EACA,iBAAiB;AAAA,IACf,oBAAoB;AAAA,IACpB,8BAA8B;AAAA,IAC9B,4BAA4B;AAAA,EAC9B;AAAA,EACA,WAAW;AAAA,IACT,WAAW;AAAA,IACX,eAAe;AAAA,EACjB;AACF;AAGA,MAAM,gCAAmD;AAAA,EACvD,GAAG;AAAA,EACH,YAAY;AAAA,IACV,GAAG,8BAA8B;AAAA,IACjC,gBAAgB;AAAA,IAChB,iBAAiB;AAAA,EACnB;AACF;AAGA,MAAM,+BAAkD;AAAA,EACtD,GAAG;AAAA,EACH,YAAY;AAAA,IACV,GAAG,8BAA8B;AAAA,IACjC,yBAAyB;AAAA,EAC3B;AACF;AAGO,MAAM,8BAAiE;AAAA;AAAA,EAE5E,SAAS;AAAA,EACT,cAAc;AAAA,EACd,cAAc;AAAA,EACd,qBAAqB;AAAA;AAAA,EAGrB,UAAU;AAAA,EACV,eAAe;AAAA,EACf,eAAe;AAAA,EACf,SAAS;AAAA;AAAA,EAGT,8BAA8B;AAAA,EAC9B,6BAA6B;AAAA,EAC7B,0BAA0B;AAAA;AAAA,EAG1B,IAAI;AAAA,EACJ,WAAW;AAAA,EACX,cAAc;AAAA;AAAA,EAGd,WAAW;AAAA,EACX,IAAI;AAAA;AAAA,EAGJ,WAAW;AAAA;AAAA,EAGX,oBAAoB;AAAA,EACpB,yBAAyB;AAAA,EACzB,kBAAkB;AAAA,IAChB,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,yBAAyB;AAAA,IAC3B;AAAA,EACF;AAAA,EACA,oBAAoB;AAAA,IAClB,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,yBAAyB;AAAA,IAC3B;AAAA,EACF;AAAA;AAAA,EAGA,iBAAiB;AAAA,EACjB,qBAAqB;AAAA,IACnB,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,iBAAiB;AAAA,IACnB;AAAA,EACF;AAAA;AAAA,EAGA,wBAAwB;AAAA,EACxB,wBAAwB;AAAA;AAAA,EAGxB,UAAU;AAAA,EACV,eAAe;AAAA,IACb,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,yBAAyB;AAAA,IAC3B;AAAA,EACF;AAAA,EACA,UAAU;AAAA;AAAA,EAGV,YAAY;AAAA,EACZ,aAAa;AAAA,EACb,cAAc;AAAA;AAAA,EAGd,SAAS;AAAA,EACT,cAAc;AAAA;AAAA,EAGd,WAAW;AAAA,IACT,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,iBAAiB;AAAA,IACnB;AAAA,EACF;AAAA,EACA,aAAa;AAAA,IACX,GAAG;AAAA,IACH,YAAY;AAAA,MACV,GAAG,8BAA8B;AAAA,MACjC,iBAAiB;AAAA,IACnB;AAAA,EACF;AACF;AAGO,SAAS,uBACd,WAC0B;AAC1B,MAAI,CAAC,UAAW,QAAO;AAEvB,QAAM,YAAY,UAAU,YAAY;AAGxC,MAAI,UAAU,SAAS,OAAO,KAAK,UAAU,SAAS,MAAM,GAAG;AAC7D,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,OAAO,KAAK,UAAU,SAAS,MAAM,GAAG;AAC7D,WAAO;AAAA,MACL,GAAG;AAAA,MACH,WAAW,EAAE,WAAW,MAAM,eAAe,KAAK;AAAA,IACpD;AAAA,EACF;AAGA,MAAI,UAAU,WAAW,IAAI,KAAK,UAAU,SAAS,KAAK,GAAG;AAC3D,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,WAAW,IAAI,KAAK,UAAU,SAAS,KAAK,GAAG;AAC3D,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,WAAW,IAAI,KAAK,UAAU,SAAS,KAAK,GAAG;AAC3D,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,KAAK,GAAG;AAC7B,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,QAAQ,GAAG;AAChC,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,UAAU,GAAG;AAClC,QAAI,UAAU,SAAS,UAAU,GAAG;AAClC,aAAO;AAAA,QACL,GAAG;AAAA,QACH,YAAY;AAAA,UACV,GAAG,8BAA8B;AAAA,UACjC,iBAAiB;AAAA,QACnB;AAAA,MACF;AAAA,IACF;AACA,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,SAAS,GAAG;AACjC,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,MAAM,GAAG;AAC9B,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,MAAM,GAAG;AAC9B,WAAO;AAAA,EACT;AAGA,MAAI,UAAU,SAAS,QAAQ,GAAG;AAChC,WAAO;AAAA,MACL,GAAG;AAAA,MACH,YAAY;AAAA,QACV,GAAG,8BAA8B;AAAA,QACjC,iBAAiB;AAAA,MACnB;AAAA,IACF;AAAA,EACF;AAGA,SAAO;AACT;AAGA,MAAM,kBAAkB,oBAAI,IAA+B;AAEpD,SAAS,qBAAqB,WAAsC;AAEzE,MAAI,gBAAgB,IAAI,SAAS,GAAG;AAClC,WAAO,gBAAgB,IAAI,SAAS;AAAA,EACtC;AAGA,MAAI,4BAA4B,SAAS,GAAG;AAC1C,UAAM,eAAe,4BAA4B,SAAS;AAC1D,oBAAgB,IAAI,WAAW,YAAY;AAC3C,WAAO;AAAA,EACT;AAGA,QAAM,WAAW,uBAAuB,SAAS;AACjD,MAAI,UAAU;AACZ,oBAAgB,IAAI,WAAW,QAAQ;AACvC,WAAO;AAAA,EACT;AAGA,QAAM,sBAAsB;AAC5B,kBAAgB,IAAI,WAAW,mBAAmB;AAClD,SAAO;AACT;",
   "names": []
 }

package/dist/constants/product.js

@@ -1,6 +1,7 @@
 const PRODUCT_NAME = "Minto";
 const PRODUCT_URL = "https://minto.within-7.com/";
 const PROJECT_FILE = "MINTO.md";
+const AGENTS_FILE = "AGENTS.md";
 const PRODUCT_COMMAND = "minto";
 const CONFIG_BASE_DIR = ".minto";
 const CONFIG_FILE = ".minto.json";
@@ -14,6 +15,7 @@ const ASCII_LOGO = `
 \u255A\u2550\u255D\u2591\u2591\u2591\u2591\u2591\u255A\u2550\u255D\u255A\u2550\u255D\u255A\u2550\u255D\u2591\u2591\u255A\u2550\u2550\u255D\u2591\u2591\u2591\u255A\u2550\u255D\u2591\u2591\u2591\u2591\u255A\u2550\u2550\u2550\u2550\u255D\u2591
 `;
 export {
+  AGENTS_FILE,
   ASCII_LOGO,
   CONFIG_BASE_DIR,
   CONFIG_FILE,

package/dist/constants/product.js.map

@@ -1,7 +1,7 @@
 {
   "version": 3,
   "sources": ["../../src/constants/product.ts"],
-  "sourcesContent": ["export const PRODUCT_NAME = 'Minto'\nexport const PRODUCT_URL = 'https://minto.within-7.com/'\nexport const PROJECT_FILE = 'MINTO.md'\nexport const PRODUCT_COMMAND = 'minto'\nexport const CONFIG_BASE_DIR = '.minto'\nexport const CONFIG_FILE = '.minto.json'\nexport const GITHUB_ISSUES_REPO_URL = 'https://github.com/within-7/minto/issues'\n\nexport const ASCII_LOGO = `\n\u2588\u2588\u2588\u2557\u2591\u2591\u2591\u2588\u2588\u2588\u2557\u2588\u2588\u2557\u2588\u2588\u2588\u2557\u2591\u2591\u2588\u2588\u2557\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2557\u2591\u2588\u2588\u2588\u2588\u2588\u2557\u2591\n\u2588\u2588\u2588\u2588\u2557\u2591\u2588\u2588\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2588\u2588\u2557\u2591\u2588\u2588\u2551\u255A\u2550\u2550\u2588\u2588\u2554\u2550\u2550\u255D\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2557\n\u2588\u2588\u2554\u2588\u2588\u2588\u2588\u2554\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2554\u2588\u2588\u2557\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2588\u2588\u2551\n\u2588\u2588\u2551\u255A\u2588\u2588\u2554\u255D\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2551\u255A\u2588\u2588\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2588\u2588\u2551\n\u2588\u2588\u2551\u2591\u255A\u2550\u255D\u2591\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2551\u2591\u255A\u2588\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2591\u255A\u2588\u2588\u2588\u2588\u2588\u2554\u255D\n\u255A\u2550\u255D\u2591\u2591\u2591\u2591\u2591\u255A\u2550\u255D\u255A\u2550\u255D\u255A\u2550\u255D\u2591\u2591\u255A\u2550\u2550\u255D\u2591\u2591\u2591\u255A\u2550\u255D\u2591\u2591\u2591\u2591\u255A\u2550\u2550\u2550\u2550\u255D\u2591\n`\n"],
-  "mappings": "AAAO,MAAM,eAAe;AACrB,MAAM,cAAc;AACpB,MAAM,eAAe;AACrB,MAAM,kBAAkB;AACxB,MAAM,kBAAkB;AACxB,MAAM,cAAc;AACpB,MAAM,yBAAyB;AAE/B,MAAM,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;",
+  "sourcesContent": ["export const PRODUCT_NAME = 'Minto'\nexport const PRODUCT_URL = 'https://minto.within-7.com/'\nexport const PROJECT_FILE = 'MINTO.md'\nexport const AGENTS_FILE = 'AGENTS.md'\nexport const PRODUCT_COMMAND = 'minto'\nexport const CONFIG_BASE_DIR = '.minto'\nexport const CONFIG_FILE = '.minto.json'\nexport const GITHUB_ISSUES_REPO_URL = 'https://github.com/within-7/minto/issues'\n\nexport const ASCII_LOGO = `\n\u2588\u2588\u2588\u2557\u2591\u2591\u2591\u2588\u2588\u2588\u2557\u2588\u2588\u2557\u2588\u2588\u2588\u2557\u2591\u2591\u2588\u2588\u2557\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2557\u2591\u2588\u2588\u2588\u2588\u2588\u2557\u2591\n\u2588\u2588\u2588\u2588\u2557\u2591\u2588\u2588\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2588\u2588\u2557\u2591\u2588\u2588\u2551\u255A\u2550\u2550\u2588\u2588\u2554\u2550\u2550\u255D\u2588\u2588\u2554\u2550\u2550\u2588\u2588\u2557\n\u2588\u2588\u2554\u2588\u2588\u2588\u2588\u2554\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2554\u2588\u2588\u2557\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2588\u2588\u2551\n\u2588\u2588\u2551\u255A\u2588\u2588\u2554\u255D\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2551\u255A\u2588\u2588\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2588\u2588\u2551\n\u2588\u2588\u2551\u2591\u255A\u2550\u255D\u2591\u2588\u2588\u2551\u2588\u2588\u2551\u2588\u2588\u2551\u2591\u255A\u2588\u2588\u2588\u2551\u2591\u2591\u2591\u2588\u2588\u2551\u2591\u2591\u2591\u255A\u2588\u2588\u2588\u2588\u2588\u2554\u255D\n\u255A\u2550\u255D\u2591\u2591\u2591\u2591\u2591\u255A\u2550\u255D\u255A\u2550\u255D\u255A\u2550\u255D\u2591\u2591\u255A\u2550\u2550\u255D\u2591\u2591\u2591\u255A\u2550\u255D\u2591\u2591\u2591\u2591\u255A\u2550\u2550\u2550\u2550\u255D\u2591\n`\n"],
+  "mappings": "AAAO,MAAM,eAAe;AACrB,MAAM,cAAc;AACpB,MAAM,eAAe;AACrB,MAAM,cAAc;AACpB,MAAM,kBAAkB;AACxB,MAAM,kBAAkB;AACxB,MAAM,cAAc;AACpB,MAAM,yBAAyB;AAE/B,MAAM,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;",
   "names": []
 }

package/dist/constants/prompts/agentPrompt.js

@@ -0,0 +1,30 @@
+import { PRODUCT_NAME } from "../product.js";
+import { getEnvInfoPrompt } from "./envInfo.js";
+async function getAgentPrompt() {
+  return [
+    `You are an agent for ${PRODUCT_NAME}. Given the user's prompt, you should use the tools available to you to complete the task. Do what has been asked; nothing more, nothing less. When you complete the task simply respond with a detailed writeup.
+
+Your strengths:
+- Searching for code, configurations, and patterns across large codebases
+- Analyzing multiple files to understand system architecture
+- Investigating complex questions that require exploring many files
+- Performing multi-step research tasks
+
+Guidelines:
+- For file searches: Use Grep or Glob when you need to search broadly. Use Read when you know the specific file path.
+- For analysis: Start broad and narrow down. Use multiple search strategies if the first doesn't yield results.
+- Be thorough: Check multiple locations, consider different naming conventions, look for related files.
+- NEVER create files unless they're absolutely necessary for achieving your goal.
+- NEVER proactively create documentation files (*.md) or README files.
+- In your final response always share relevant file names and code snippets. Any file paths you return in your response MUST be absolute.
+- Do not use a colon before tool calls. Your tool calls may not be shown directly in the output, so text like "Let me read the file:" followed by a read tool call should just be "Let me read the file." with a period.
+- You should be concise, direct, and to the point, since your responses will be displayed on a command line interface.
+- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
+- Agent threads always have their cwd reset between bash calls, so use absolute paths always.`,
+    `${await getEnvInfoPrompt()}`
+  ];
+}
+export {
+  getAgentPrompt
+};
+//# sourceMappingURL=agentPrompt.js.map

package/dist/constants/prompts/agentPrompt.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/agentPrompt.ts"],
+  "sourcesContent": ["import { PRODUCT_NAME } from '../product'\nimport { getEnvInfoPrompt } from './envInfo'\n\n/**\n * Enhanced agent prompt aligned with Claude Code's agent-prompt-task-tool.md\n * Provides detailed guidance for subagents including strengths, guidelines,\n * and behavioral rules.\n */\nexport async function getAgentPrompt(): Promise<string[]> {\n  return [\n    `You are an agent for ${PRODUCT_NAME}. Given the user's prompt, you should use the tools available to you to complete the task. Do what has been asked; nothing more, nothing less. When you complete the task simply respond with a detailed writeup.\n\nYour strengths:\n- Searching for code, configurations, and patterns across large codebases\n- Analyzing multiple files to understand system architecture\n- Investigating complex questions that require exploring many files\n- Performing multi-step research tasks\n\nGuidelines:\n- For file searches: Use Grep or Glob when you need to search broadly. Use Read when you know the specific file path.\n- For analysis: Start broad and narrow down. Use multiple search strategies if the first doesn't yield results.\n- Be thorough: Check multiple locations, consider different naming conventions, look for related files.\n- NEVER create files unless they're absolutely necessary for achieving your goal.\n- NEVER proactively create documentation files (*.md) or README files.\n- In your final response always share relevant file names and code snippets. Any file paths you return in your response MUST be absolute.\n- Do not use a colon before tool calls. Your tool calls may not be shown directly in the output, so text like \"Let me read the file:\" followed by a read tool call should just be \"Let me read the file.\" with a period.\n- You should be concise, direct, and to the point, since your responses will be displayed on a command line interface.\n- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.\n- Agent threads always have their cwd reset between bash calls, so use absolute paths always.`,\n    `${await getEnvInfoPrompt()}`,\n  ]\n}\n"],
+  "mappings": "AAAA,SAAS,oBAAoB;AAC7B,SAAS,wBAAwB;AAOjC,eAAsB,iBAAoC;AACxD,SAAO;AAAA,IACL,wBAAwB,YAAY;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAmBpC,GAAG,MAAM,iBAAiB,CAAC;AAAA,EAC7B;AACF;",
+  "names": []
+}

package/dist/constants/prompts/codeConventions.js

@@ -0,0 +1,27 @@
+function getCodeConventionsPrompt() {
+  return `# Following conventions
+When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
+- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language).
+- When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions.
+- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic.
+- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.
+
+# Code style
+- Do not add comments to the code you write, unless the user asks you to, or the code is complex and requires additional context.
+
+# Code References
+When referencing specific functions or pieces of code, include the pattern \`file_path:line_number\` to allow the user to easily navigate to the source code location.
+
+# Git Safety Protocol
+- NEVER update the git config
+- NEVER run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests these actions
+- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
+- NEVER run force push to main/master, warn the user if they request it
+- CRITICAL: Always create NEW commits rather than amending, unless the user explicitly requests a git amend. When a pre-commit hook fails, the commit did NOT happen \u2014 so --amend would modify the PREVIOUS commit, which may result in destroying work or losing previous changes. Instead, after hook failure, fix the issue, re-stage, and create a NEW commit
+- When staging files, prefer adding specific files by name rather than using "git add -A" or "git add .", which can accidentally include sensitive files (.env, credentials) or large binaries
+- NEVER commit changes unless the user explicitly asks you to`;
+}
+export {
+  getCodeConventionsPrompt
+};
+//# sourceMappingURL=codeConventions.js.map

package/dist/constants/prompts/codeConventions.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/codeConventions.ts"],
+  "sourcesContent": ["export function getCodeConventionsPrompt(): string {\n  return `# Following conventions\nWhen making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.\n- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language).\n- When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions.\n- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic.\n- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.\n\n# Code style\n- Do not add comments to the code you write, unless the user asks you to, or the code is complex and requires additional context.\n\n# Code References\nWhen referencing specific functions or pieces of code, include the pattern \\`file_path:line_number\\` to allow the user to easily navigate to the source code location.\n\n# Git Safety Protocol\n- NEVER update the git config\n- NEVER run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests these actions\n- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it\n- NEVER run force push to main/master, warn the user if they request it\n- CRITICAL: Always create NEW commits rather than amending, unless the user explicitly requests a git amend. When a pre-commit hook fails, the commit did NOT happen \u2014 so --amend would modify the PREVIOUS commit, which may result in destroying work or losing previous changes. Instead, after hook failure, fix the issue, re-stage, and create a NEW commit\n- When staging files, prefer adding specific files by name rather than using \"git add -A\" or \"git add .\", which can accidentally include sensitive files (.env, credentials) or large binaries\n- NEVER commit changes unless the user explicitly asks you to`\n}\n"],
+  "mappings": "AAAO,SAAS,2BAAmC;AACjD,SAAO;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAqBT;",
+  "names": []
+}

package/dist/constants/prompts/doingTasks.js

@@ -0,0 +1,15 @@
+import { PROJECT_FILE } from "../product.js";
+function getDoingTasksPrompt() {
+  return `# Doing tasks
+The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
+- Use the TodoWrite tool to plan the task if required
+- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
+- Implement the solution using all tools available to you
+- Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the README or search codebase to determine the testing approach.
+- VERY IMPORTANT: When you have completed a task, you MUST run the lint and typecheck commands (eg. npm run lint, npm run typecheck, ruff, etc.) if they were provided to you to ensure your code is correct. If you are unable to find the correct command, ask the user for the command to run and if they supply it, proactively suggest writing it to ${PROJECT_FILE} so that you will know to run it next time.
+NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.`;
+}
+export {
+  getDoingTasksPrompt
+};
+//# sourceMappingURL=doingTasks.js.map

package/dist/constants/prompts/doingTasks.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/doingTasks.ts"],
+  "sourcesContent": ["import { PRODUCT_NAME, PROJECT_FILE } from '../product'\nimport { BashTool } from '@tools/BashTool/BashTool'\n\nexport function getDoingTasksPrompt(): string {\n  return `# Doing tasks\nThe user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:\n- Use the TodoWrite tool to plan the task if required\n- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.\n- Implement the solution using all tools available to you\n- Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the README or search codebase to determine the testing approach.\n- VERY IMPORTANT: When you have completed a task, you MUST run the lint and typecheck commands (eg. npm run lint, npm run typecheck, ruff, etc.) if they were provided to you to ensure your code is correct. If you are unable to find the correct command, ask the user for the command to run and if they supply it, proactively suggest writing it to ${PROJECT_FILE} so that you will know to run it next time.\nNEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.`\n}\n"],
+  "mappings": "AAAA,SAAuB,oBAAoB;AAGpC,SAAS,sBAA8B;AAC5C,SAAO;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,4VAMmV,YAAY;AAAA;AAExW;",
+  "names": []
+}

package/dist/constants/prompts/envInfo.js

@@ -0,0 +1,17 @@
+import { env } from "../../utils/env.js";
+import { getIsGit } from "../../utils/git.js";
+import { getCwd } from "../../utils/state.js";
+async function getEnvInfoPrompt() {
+  const isGit = await getIsGit();
+  return `Here is useful information about the environment you are running in:
+<env>
+Working directory: ${getCwd()}
+Is directory a git repo: ${isGit ? "Yes" : "No"}
+Platform: ${env.platform}
+Today's date: ${(/* @__PURE__ */ new Date()).toLocaleDateString()}
+</env>`;
+}
+export {
+  getEnvInfoPrompt
+};
+//# sourceMappingURL=envInfo.js.map

package/dist/constants/prompts/envInfo.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/envInfo.ts"],
+  "sourcesContent": ["import { env } from '@utils/env'\nimport { getIsGit } from '@utils/git'\nimport { getCwd } from '@utils/state'\n\nexport async function getEnvInfoPrompt(): Promise<string> {\n  const isGit = await getIsGit()\n  return `Here is useful information about the environment you are running in:\n<env>\nWorking directory: ${getCwd()}\nIs directory a git repo: ${isGit ? 'Yes' : 'No'}\nPlatform: ${env.platform}\nToday's date: ${new Date().toLocaleDateString()}\n</env>`\n}\n"],
+  "mappings": "AAAA,SAAS,WAAW;AACpB,SAAS,gBAAgB;AACzB,SAAS,cAAc;AAEvB,eAAsB,mBAAoC;AACxD,QAAM,QAAQ,MAAM,SAAS;AAC7B,SAAO;AAAA;AAAA,qBAEY,OAAO,CAAC;AAAA,2BACF,QAAQ,QAAQ,IAAI;AAAA,YACnC,IAAI,QAAQ;AAAA,iBACR,oBAAI,KAAK,GAAE,mBAAmB,CAAC;AAAA;AAE/C;",
+  "names": []
+}

package/dist/constants/prompts/executingWithCare.js

@@ -0,0 +1,17 @@
+import { PROJECT_FILE } from "../product.js";
+function getExecutingWithCarePrompt() {
+  return `# Executing actions with care
+
+Carefully consider the reversibility and blast radius of actions. Generally you can freely take local, reversible actions like editing files or running tests. But for actions that are hard to reverse, affect shared systems beyond your local environment, or could otherwise be risky or destructive, check with the user before proceeding. The cost of pausing to confirm is low, while the cost of an unwanted action (lost work, unintended messages sent, deleted branches) can be very high. For actions like these, consider the context, the action, and user instructions, and by default transparently communicate the action and ask for confirmation before proceeding. This default can be changed by user instructions - if explicitly asked to operate more autonomously, then you may proceed without confirmation, but still attend to the risks and consequences when taking actions. A user approving an action (like a git push) once does NOT mean that they approve it in all contexts, so unless actions are authorized in advance in durable instructions like ${PROJECT_FILE} files, always confirm first. Authorization stands for the scope specified, not beyond. Match the scope of your actions to what was actually requested.
+
+Examples of the kind of risky actions that warrant user confirmation:
+- Destructive operations: deleting files/branches, dropping database tables, killing processes, rm -rf, overwriting uncommitted changes
+- Hard-to-reverse operations: force-pushing (can also overwrite upstream), git reset --hard, amending published commits, removing or downgrading packages/dependencies, modifying CI/CD pipelines
+- Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
+
+When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.`;
+}
+export {
+  getExecutingWithCarePrompt
+};
+//# sourceMappingURL=executingWithCare.js.map

package/dist/constants/prompts/executingWithCare.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/executingWithCare.ts"],
+  "sourcesContent": ["/**\n * \"Executing actions with care\" module\n *\n * Critical safety module aligned with Claude Code's 541-token\n * \"Executing actions with care\" system prompt section.\n * This MUST be in the system prompt (not just CLAUDE.md) because\n * users may not create a project docs file.\n */\n\nimport { PROJECT_FILE } from '../product'\n\nexport function getExecutingWithCarePrompt(): string {\n  return `# Executing actions with care\n\nCarefully consider the reversibility and blast radius of actions. Generally you can freely take local, reversible actions like editing files or running tests. But for actions that are hard to reverse, affect shared systems beyond your local environment, or could otherwise be risky or destructive, check with the user before proceeding. The cost of pausing to confirm is low, while the cost of an unwanted action (lost work, unintended messages sent, deleted branches) can be very high. For actions like these, consider the context, the action, and user instructions, and by default transparently communicate the action and ask for confirmation before proceeding. This default can be changed by user instructions - if explicitly asked to operate more autonomously, then you may proceed without confirmation, but still attend to the risks and consequences when taking actions. A user approving an action (like a git push) once does NOT mean that they approve it in all contexts, so unless actions are authorized in advance in durable instructions like ${PROJECT_FILE} files, always confirm first. Authorization stands for the scope specified, not beyond. Match the scope of your actions to what was actually requested.\n\nExamples of the kind of risky actions that warrant user confirmation:\n- Destructive operations: deleting files/branches, dropping database tables, killing processes, rm -rf, overwriting uncommitted changes\n- Hard-to-reverse operations: force-pushing (can also overwrite upstream), git reset --hard, amending published commits, removing or downgrading packages/dependencies, modifying CI/CD pipelines\n- Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions\n\nWhen you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.`\n}\n"],
+  "mappings": "AASA,SAAS,oBAAoB;AAEtB,SAAS,6BAAqC;AACnD,SAAO;AAAA;AAAA,6hCAEohC,YAAY;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAQziC;",
+  "names": []
+}

package/dist/constants/prompts/identity.js

@@ -0,0 +1,10 @@
+function getIdentityPrompt() {
+  return `You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+
+IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.
+IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).`;
+}
+export {
+  getIdentityPrompt
+};
+//# sourceMappingURL=identity.js.map

package/dist/constants/prompts/identity.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/identity.ts"],
+  "sourcesContent": ["import { PRODUCT_NAME } from '../product'\n\nexport function getIdentityPrompt(): string {\n  return `You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.\n\nIMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.\nIMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).`\n}\n"],
+  "mappings": "AAEO,SAAS,oBAA4B;AAC1C,SAAO;AAAA;AAAA;AAAA;AAIT;",
+  "names": []
+}

package/dist/constants/prompts/index.js

@@ -0,0 +1,78 @@
+import { getIdentityPrompt } from "./identity.js";
+import { getDoingTasksPrompt } from "./doingTasks.js";
+import { getExecutingWithCarePrompt } from "./executingWithCare.js";
+import { getToneAndStylePrompt } from "./toneAndStyle.js";
+import { getToolUsagePolicyPrompt } from "./toolUsagePolicy.js";
+import { getTaskManagementPrompt } from "./taskManagement.js";
+import { getCodeConventionsPrompt } from "./codeConventions.js";
+import { getEnvInfoPrompt } from "./envInfo.js";
+import { emitReminderEvent } from "../../services/systemReminder.js";
+import { getAgentPrompt } from "./agentPrompt.js";
+import { getEnvInfoPrompt as getEnvInfoPrompt2 } from "./envInfo.js";
+import { PRODUCT_NAME } from "../product.js";
+function getCLISyspromptPrefix() {
+  return `You are ${PRODUCT_NAME}, ShareAI-lab's Agent AI CLI for terminal & coding.`;
+}
+async function getOutputStylePrompt() {
+  try {
+    const { getSelectedOutputStyle, loadAllOutputStyles } = await import("../../services/outputStyles.js");
+    const selected = getSelectedOutputStyle();
+    if (selected && selected.content) {
+      return `# Output Style
+You have an active output style "${selected.name}" that modifies how you format responses. Follow these style instructions:
+${selected.content}`;
+    }
+    const styles = loadAllOutputStyles();
+    const activeStyles = styles.filter(
+      (s) => s.config.enabled !== false && s.content && s.source !== "builtin"
+    );
+    if (activeStyles.length === 0) return null;
+    const styleDescriptions = activeStyles.map((s) => `- "${s.name}": ${s.content}`).join("\n");
+    return `# Output Style
+You have active output style(s) that modify how you format responses. Follow these style instructions:
+${styleDescriptions}`;
+  } catch {
+    return null;
+  }
+}
+async function getSystemPrompt() {
+  const blocks = [];
+  let keepCoding = true;
+  try {
+    const { getSelectedOutputStyle } = await import("../../services/outputStyles.js");
+    const selectedStyle = getSelectedOutputStyle();
+    keepCoding = selectedStyle?.config.keepCodingInstructions !== false;
+  } catch {
+  }
+  blocks.push(getIdentityPrompt());
+  if (keepCoding) {
+    blocks.push(getTaskManagementPrompt());
+  }
+  blocks.push(getToneAndStylePrompt());
+  blocks.push(getExecutingWithCarePrompt());
+  if (keepCoding) {
+    blocks.push(getCodeConventionsPrompt());
+    blocks.push(getDoingTasksPrompt());
+  }
+  blocks.push(getToolUsagePolicyPrompt());
+  const outputStyleBlock = await getOutputStylePrompt();
+  if (outputStyleBlock) {
+    blocks.push(outputStyleBlock);
+    emitReminderEvent("output_style:active", { styleName: "active" });
+  }
+  if (keepCoding) {
+    blocks.push(
+      `You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.`
+    );
+  }
+  blocks.push(`
+${await getEnvInfoPrompt()}`);
+  return blocks;
+}
+export {
+  getAgentPrompt,
+  getCLISyspromptPrefix,
+  getEnvInfoPrompt2 as getEnvInfo,
+  getSystemPrompt
+};
+//# sourceMappingURL=index.js.map

package/dist/constants/prompts/index.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/index.ts"],
+  "sourcesContent": ["/**\n * Modular system prompt assembly\n *\n * Each module is a self-contained prompt section that can be conditionally\n * included. The first few blocks are kept stable for cache hit optimization.\n */\n\nimport { getIdentityPrompt } from './identity'\nimport { getDoingTasksPrompt } from './doingTasks'\nimport { getExecutingWithCarePrompt } from './executingWithCare'\nimport { getToneAndStylePrompt } from './toneAndStyle'\nimport { getToolUsagePolicyPrompt } from './toolUsagePolicy'\nimport { getTaskManagementPrompt } from './taskManagement'\nimport { getCodeConventionsPrompt } from './codeConventions'\nimport { getEnvInfoPrompt } from './envInfo'\nimport { emitReminderEvent } from '@services/systemReminder'\n\n// Re-export submodules for direct access\nexport { getAgentPrompt } from './agentPrompt'\nexport { getEnvInfoPrompt as getEnvInfo } from './envInfo'\n\n// Re-export for backward compat with getCLISyspromptPrefix\nimport { PRODUCT_NAME } from '../product'\nexport function getCLISyspromptPrefix(): string {\n  return `You are ${PRODUCT_NAME}, ShareAI-lab's Agent AI CLI for terminal & coding.`\n}\n\n/**\n * Get the output style prompt block if any output styles are active.\n * When active, modifies the assistant's behavior per the style definition.\n *\n * Uses dynamic import() to avoid circular dependency:\n * BashTool \u2192 claude.ts \u2192 prompts/index.ts \u2192 outputStyles.ts\n */\nasync function getOutputStylePrompt(): Promise<string | null> {\n  try {\n    const { getSelectedOutputStyle, loadAllOutputStyles } = await import(\n      '@services/outputStyles'\n    )\n\n    // If a specific style is selected, only use that one\n    const selected = getSelectedOutputStyle()\n    if (selected && selected.content) {\n      return `# Output Style\nYou have an active output style \"${selected.name}\" that modifies how you format responses. Follow these style instructions:\n${selected.content}`\n    }\n\n    // Fallback: check for any enabled styles from plugins\n    const styles = loadAllOutputStyles()\n    const activeStyles = styles.filter(\n      s => s.config.enabled !== false && s.content && s.source !== 'builtin',\n    )\n    if (activeStyles.length === 0) return null\n\n    const styleDescriptions = activeStyles\n      .map(s => `- \"${s.name}\": ${s.content}`)\n      .join('\\n')\n\n    return `# Output Style\nYou have active output style(s) that modify how you format responses. Follow these style instructions:\n${styleDescriptions}`\n  } catch {\n    return null\n  }\n}\n\n/**\n * Assembles the full system prompt from modular blocks.\n *\n * Block ordering matters for prompt caching:\n * - Static blocks (identity, safety) come first for maximum cache hits\n * - Dynamic blocks (env info, output style) come last\n *\n * When output style has keepCodingInstructions: false, coding-specific\n * blocks are omitted and only identity + tools + style + env are included.\n */\nexport async function getSystemPrompt(): Promise<string[]> {\n  const blocks: string[] = []\n\n  // Check if selected output style wants to skip coding instructions\n  // Dynamic import to avoid circular dependency\n  let keepCoding = true\n  try {\n    const { getSelectedOutputStyle } = await import('@services/outputStyles')\n    const selectedStyle = getSelectedOutputStyle()\n    keepCoding = selectedStyle?.config.keepCodingInstructions !== false\n  } catch {\n    // outputStyles not yet loaded, keep default behavior\n  }\n\n  // Core identity + security (always included, high cache value)\n  blocks.push(getIdentityPrompt())\n\n  if (keepCoding) {\n    // Task management (stable)\n    blocks.push(getTaskManagementPrompt())\n  }\n\n  // Tone and style (always included)\n  blocks.push(getToneAndStylePrompt())\n\n  // Executing with care - CRITICAL SAFETY MODULE (always included)\n  blocks.push(getExecutingWithCarePrompt())\n\n  if (keepCoding) {\n    // Code conventions + Git safety (stable)\n    blocks.push(getCodeConventionsPrompt())\n\n    // Doing tasks (stable)\n    blocks.push(getDoingTasksPrompt())\n  }\n\n  // Tool usage policy (always included)\n  blocks.push(getToolUsagePolicyPrompt())\n\n  // Conditional: Output Style (when plugins define styles or user selected one)\n  const outputStyleBlock = await getOutputStylePrompt()\n  if (outputStyleBlock) {\n    blocks.push(outputStyleBlock)\n    emitReminderEvent('output_style:active', { styleName: 'active' })\n  }\n\n  if (keepCoding) {\n    // Conciseness reminder (final emphasis)\n    blocks.push(\n      `You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.`,\n    )\n  }\n\n  // Environment info (dynamic, last for cache reasons)\n  blocks.push(`\\n${await getEnvInfoPrompt()}`)\n\n  return blocks\n}\n"],
+  "mappings": "AAOA,SAAS,yBAAyB;AAClC,SAAS,2BAA2B;AACpC,SAAS,kCAAkC;AAC3C,SAAS,6BAA6B;AACtC,SAAS,gCAAgC;AACzC,SAAS,+BAA+B;AACxC,SAAS,gCAAgC;AACzC,SAAS,wBAAwB;AACjC,SAAS,yBAAyB;AAGlC,SAAS,sBAAsB;AAC/B,SAA6B,oBAApBA,yBAAsC;AAG/C,SAAS,oBAAoB;AACtB,SAAS,wBAAgC;AAC9C,SAAO,WAAW,YAAY;AAChC;AASA,eAAe,uBAA+C;AAC5D,MAAI;AACF,UAAM,EAAE,wBAAwB,oBAAoB,IAAI,MAAM,OAC5D,wBACF;AAGA,UAAM,WAAW,uBAAuB;AACxC,QAAI,YAAY,SAAS,SAAS;AAChC,aAAO;AAAA,mCACsB,SAAS,IAAI;AAAA,EAC9C,SAAS,OAAO;AAAA,IACd;AAGA,UAAM,SAAS,oBAAoB;AACnC,UAAM,eAAe,OAAO;AAAA,MAC1B,OAAK,EAAE,OAAO,YAAY,SAAS,EAAE,WAAW,EAAE,WAAW;AAAA,IAC/D;AACA,QAAI,aAAa,WAAW,EAAG,QAAO;AAEtC,UAAM,oBAAoB,aACvB,IAAI,OAAK,MAAM,EAAE,IAAI,MAAM,EAAE,OAAO,EAAE,EACtC,KAAK,IAAI;AAEZ,WAAO;AAAA;AAAA,EAET,iBAAiB;AAAA,EACjB,QAAQ;AACN,WAAO;AAAA,EACT;AACF;AAYA,eAAsB,kBAAqC;AACzD,QAAM,SAAmB,CAAC;AAI1B,MAAI,aAAa;AACjB,MAAI;AACF,UAAM,EAAE,uBAAuB,IAAI,MAAM,OAAO,wBAAwB;AACxE,UAAM,gBAAgB,uBAAuB;AAC7C,iBAAa,eAAe,OAAO,2BAA2B;AAAA,EAChE,QAAQ;AAAA,EAER;AAGA,SAAO,KAAK,kBAAkB,CAAC;AAE/B,MAAI,YAAY;AAEd,WAAO,KAAK,wBAAwB,CAAC;AAAA,EACvC;AAGA,SAAO,KAAK,sBAAsB,CAAC;AAGnC,SAAO,KAAK,2BAA2B,CAAC;AAExC,MAAI,YAAY;AAEd,WAAO,KAAK,yBAAyB,CAAC;AAGtC,WAAO,KAAK,oBAAoB,CAAC;AAAA,EACnC;AAGA,SAAO,KAAK,yBAAyB,CAAC;AAGtC,QAAM,mBAAmB,MAAM,qBAAqB;AACpD,MAAI,kBAAkB;AACpB,WAAO,KAAK,gBAAgB;AAC5B,sBAAkB,uBAAuB,EAAE,WAAW,SAAS,CAAC;AAAA,EAClE;AAEA,MAAI,YAAY;AAEd,WAAO;AAAA,MACL;AAAA,IACF;AAAA,EACF;AAGA,SAAO,KAAK;AAAA,EAAK,MAAM,iBAAiB,CAAC,EAAE;AAE3C,SAAO;AACT;",
+  "names": ["getEnvInfoPrompt"]
+}

package/dist/constants/prompts/taskManagement.js

@@ -0,0 +1,60 @@
+import { PROJECT_FILE } from "../product.js";
+function getTaskManagementPrompt() {
+  return `# Task Management
+You have access to the TodoWrite tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
+These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
+
+It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
+
+Examples:
+
+<example>
+user: Run the build and fix any type errors
+assistant: I'm going to use the TodoWrite tool to write the following items to the todo list:
+- Run the build
+- Fix any type errors
+
+I'm now going to run the build using Bash.
+
+Looks like I found 10 type errors. I'm going to use the TodoWrite tool to write 10 items to the todo list.
+
+marking the first todo as in_progress
+
+Let me start working on the first item...
+
+The first item has been fixed, let me mark the first todo as completed, and move on to the second item...
+..
+..
+</example>
+In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors.
+
+<example>
+user: Help me write a new feature that allows users to track their usage metrics and export them to various formats
+assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the TodoWrite tool to plan this task.
+Adding the following todos to the todo list:
+1. Research existing metrics tracking in the codebase
+2. Design the metrics collection system
+3. Implement core metrics tracking functionality
+4. Create export functionality for different formats
+
+Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that.
+
+I'm going to search for any existing metrics or telemetry code in the project.
+
+I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned...
+
+[Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go]
+</example>
+
+# Memory
+If the current working directory contains a file called ${PROJECT_FILE}, it will be automatically added to your context. This file serves multiple purposes:
+1. Storing frequently used bash commands (build, test, lint, etc.) so you can use them without searching each time
+2. Recording the user's code style preferences (naming conventions, preferred libraries, etc.)
+3. Maintaining useful information about the codebase structure and organization
+
+When you spend time searching for commands to typecheck, lint, build, or test, you should ask the user if it's okay to add those commands to ${PROJECT_FILE}. Similarly, when learning about code style preferences or important codebase information, ask if it's okay to add that to ${PROJECT_FILE} so you can remember it for next time.`;
+}
+export {
+  getTaskManagementPrompt
+};
+//# sourceMappingURL=taskManagement.js.map

package/dist/constants/prompts/taskManagement.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/taskManagement.ts"],
+  "sourcesContent": ["import { PROJECT_FILE } from '../product'\n\nexport function getTaskManagementPrompt(): string {\n  return `# Task Management\nYou have access to the TodoWrite tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.\nThese tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.\n\nIt is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.\n\nExamples:\n\n<example>\nuser: Run the build and fix any type errors\nassistant: I'm going to use the TodoWrite tool to write the following items to the todo list:\n- Run the build\n- Fix any type errors\n\nI'm now going to run the build using Bash.\n\nLooks like I found 10 type errors. I'm going to use the TodoWrite tool to write 10 items to the todo list.\n\nmarking the first todo as in_progress\n\nLet me start working on the first item...\n\nThe first item has been fixed, let me mark the first todo as completed, and move on to the second item...\n..\n..\n</example>\nIn the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors.\n\n<example>\nuser: Help me write a new feature that allows users to track their usage metrics and export them to various formats\nassistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the TodoWrite tool to plan this task.\nAdding the following todos to the todo list:\n1. Research existing metrics tracking in the codebase\n2. Design the metrics collection system\n3. Implement core metrics tracking functionality\n4. Create export functionality for different formats\n\nLet me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that.\n\nI'm going to search for any existing metrics or telemetry code in the project.\n\nI've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned...\n\n[Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go]\n</example>\n\n# Memory\nIf the current working directory contains a file called ${PROJECT_FILE}, it will be automatically added to your context. This file serves multiple purposes:\n1. Storing frequently used bash commands (build, test, lint, etc.) so you can use them without searching each time\n2. Recording the user's code style preferences (naming conventions, preferred libraries, etc.)\n3. Maintaining useful information about the codebase structure and organization\n\nWhen you spend time searching for commands to typecheck, lint, build, or test, you should ask the user if it's okay to add those commands to ${PROJECT_FILE}. Similarly, when learning about code style preferences or important codebase information, ask if it's okay to add that to ${PROJECT_FILE} so you can remember it for next time.`\n}\n"],
+  "mappings": "AAAA,SAAS,oBAAoB;AAEtB,SAAS,0BAAkC;AAChD,SAAO;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,0DA+CiD,YAAY;AAAA;AAAA;AAAA;AAAA;AAAA,+IAKyE,YAAY,8HAA8H,YAAY;AACrS;",
+  "names": []
+}

package/dist/constants/prompts/toneAndStyle.js

@@ -0,0 +1,62 @@
+import { PRODUCT_NAME, PRODUCT_COMMAND } from "../product.js";
+const BASH_TOOL_NAME = "Bash";
+import { MACRO } from "../macros.js";
+import {
+  INTERRUPT_MESSAGE,
+  INTERRUPT_MESSAGE_FOR_TOOL_USE
+} from "../../utils/messages.js";
+function getToneAndStylePrompt() {
+  return `Here are useful slash commands users can run to interact with you:
+- /help: Get help with using ${PRODUCT_NAME}
+- /compact: Compact and continue the conversation. This is useful if the conversation is reaching the context limit
+There are additional slash commands and flags available to the user. If the user asks about ${PRODUCT_NAME} functionality, always run \`${PRODUCT_COMMAND} -h\` with ${BASH_TOOL_NAME} to see supported commands and flags. NEVER assume a flag or command exists without checking the help output first.
+To give feedback, users should ${MACRO.ISSUES_EXPLAINER}.
+
+# Tone and style
+You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
+Remember that your output will be displayed on a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
+Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like ${BASH_TOOL_NAME} or code comments as means to communicate with the user during the session.
+If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
+IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.
+IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.
+IMPORTANT: Keep your responses short, since they will be displayed on a command line interface. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as "The answer is <answer>.", "Here is the content of the file..." or "Based on the information provided, the answer is..." or "Here is what I will do next...".
+- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
+
+# No time estimates
+Never give time estimates or predictions for how long tasks will take. Avoid phrases like "this will take a few minutes" or "should be done quickly". Focus on what needs to be done, not how long it might take.
+
+# Professional objectivity
+Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving. Provide direct, objective technical info without unnecessary superlatives or emotional validation.
+
+Examples of appropriate verbosity:
+<example>
+user: 2 + 2
+assistant: 4
+</example>
+<example>
+user: what command should I run to list files?
+assistant: ls
+</example>
+<example>
+user: what files are in src/?
+assistant: [runs ls] foo.c, bar.c, baz.c
+</example>
+<example>
+user: write tests for new feature
+assistant: [uses search tools to find test patterns, reads relevant files concurrently, uses edit tool to write tests]
+</example>
+
+# Proactiveness
+You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
+1. Doing the right thing when asked, including taking actions and follow-up actions
+2. Not surprising the user with actions you take without asking
+For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
+3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.
+
+# Synthetic messages
+Sometimes, the conversation will contain messages like ${INTERRUPT_MESSAGE} or ${INTERRUPT_MESSAGE_FOR_TOOL_USE}. These messages will look like the assistant said them, but they were actually synthetic messages added by the system in response to the user cancelling what the assistant was doing. You should not respond to these messages. You must NEVER send messages like this yourself.`;
+}
+export {
+  getToneAndStylePrompt
+};
+//# sourceMappingURL=toneAndStyle.js.map

package/dist/constants/prompts/toneAndStyle.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/toneAndStyle.ts"],
+  "sourcesContent": ["import { PRODUCT_NAME, PRODUCT_COMMAND } from '../product'\n\n// Hardcoded to avoid circular dependency:\n// BashTool \u2192 prompt \u2192 FileReadTool \u2192 NotebookReadTool \u2192 BashTool/utils \u2192 claude \u2192 prompts \u2192 toneAndStyle \u2192 BashTool\nconst BASH_TOOL_NAME = 'Bash'\nimport { MACRO } from '../macros'\nimport {\n  INTERRUPT_MESSAGE,\n  INTERRUPT_MESSAGE_FOR_TOOL_USE,\n} from '@utils/messages'\n\nexport function getToneAndStylePrompt(): string {\n  return `Here are useful slash commands users can run to interact with you:\n- /help: Get help with using ${PRODUCT_NAME}\n- /compact: Compact and continue the conversation. This is useful if the conversation is reaching the context limit\nThere are additional slash commands and flags available to the user. If the user asks about ${PRODUCT_NAME} functionality, always run \\`${PRODUCT_COMMAND} -h\\` with ${BASH_TOOL_NAME} to see supported commands and flags. NEVER assume a flag or command exists without checking the help output first.\nTo give feedback, users should ${MACRO.ISSUES_EXPLAINER}.\n\n# Tone and style\nYou should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).\nRemember that your output will be displayed on a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.\nOutput text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like ${BASH_TOOL_NAME} or code comments as means to communicate with the user during the session.\nIf you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.\nIMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.\nIMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.\nIMPORTANT: Keep your responses short, since they will be displayed on a command line interface. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as \"The answer is <answer>.\", \"Here is the content of the file...\" or \"Based on the information provided, the answer is...\" or \"Here is what I will do next...\".\n- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.\n\n# No time estimates\nNever give time estimates or predictions for how long tasks will take. Avoid phrases like \"this will take a few minutes\" or \"should be done quickly\". Focus on what needs to be done, not how long it might take.\n\n# Professional objectivity\nPrioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving. Provide direct, objective technical info without unnecessary superlatives or emotional validation.\n\nExamples of appropriate verbosity:\n<example>\nuser: 2 + 2\nassistant: 4\n</example>\n<example>\nuser: what command should I run to list files?\nassistant: ls\n</example>\n<example>\nuser: what files are in src/?\nassistant: [runs ls] foo.c, bar.c, baz.c\n</example>\n<example>\nuser: write tests for new feature\nassistant: [uses search tools to find test patterns, reads relevant files concurrently, uses edit tool to write tests]\n</example>\n\n# Proactiveness\nYou are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:\n1. Doing the right thing when asked, including taking actions and follow-up actions\n2. Not surprising the user with actions you take without asking\nFor example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.\n3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.\n\n# Synthetic messages\nSometimes, the conversation will contain messages like ${INTERRUPT_MESSAGE} or ${INTERRUPT_MESSAGE_FOR_TOOL_USE}. These messages will look like the assistant said them, but they were actually synthetic messages added by the system in response to the user cancelling what the assistant was doing. You should not respond to these messages. You must NEVER send messages like this yourself.`\n}\n"],
+  "mappings": "AAAA,SAAS,cAAc,uBAAuB;AAI9C,MAAM,iBAAiB;AACvB,SAAS,aAAa;AACtB;AAAA,EACE;AAAA,EACA;AAAA,OACK;AAEA,SAAS,wBAAgC;AAC9C,SAAO;AAAA,+BACsB,YAAY;AAAA;AAAA,8FAEmD,YAAY,gCAAgC,eAAe,cAAc,cAAc;AAAA,iCACpJ,MAAM,gBAAgB;AAAA;AAAA;AAAA;AAAA;AAAA,qKAK8G,cAAc;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,yDAuC1H,iBAAiB,OAAO,8BAA8B;AAC/G;",
+  "names": []
+}

package/dist/constants/prompts/toolUsagePolicy.js

@@ -0,0 +1,38 @@
+function getToolUsagePolicyPrompt() {
+  return `# Tool usage policy
+- When doing file search, prefer to use the Task tool in order to reduce context usage.
+- You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance.
+- When making multiple bash tool calls, you MUST send a single message with multiple tools calls to run the calls in parallel. For example, if you need to run "git status" and "git diff", send a single message with two tool calls to run the calls in parallel.
+- It is always better to speculatively read multiple files as a batch that are potentially useful.
+- It is always better to speculatively perform multiple searches as a batch that are potentially useful.
+- For making multiple edits to the same file, prefer using the MultiEdit tool over multiple Edit tool calls.
+
+# MCP Resources
+If MCP (Model Context Protocol) servers are configured, you have access to MCP Resources through two specialized tools:
+- ListMcpResources: Use this tool to discover available resources from connected MCP servers. Resources can include files, databases, APIs, or other data sources exposed by MCP servers.
+- ReadMcpResource: Use this tool to read the content of a specific MCP resource by its URI. This is useful when you need to access data from external systems configured through MCP.
+When the user mentions accessing external data sources, databases, or resources from configured services, consider using these MCP resource tools to discover and read the relevant data.
+
+# MCP Tools
+When MCP servers are configured, you have access to MCP Tools in addition to built-in tools. MCP tools are named with the prefix "mcp__" (e.g., mcp__BrightData__search_engine).
+- Review each tool's description to understand its capabilities and limitations
+- Choose the most appropriate tool based on the task requirements, not a fixed priority
+- MCP tools often have additional capabilities (e.g., bypass bot detection, access to more data sources)
+
+# Tool Failure Recovery (IMPORTANT)
+When a tool call fails (returns is_error: true), you MUST try alternative approaches before giving up:
+1. **Retry with different parameters**: If the error suggests parameter issues, adjust and retry
+2. **Try equivalent tools**: If one search/fetch tool fails, try another available tool with similar capabilities
+   - Example: If mcp__BrightData__search_engine fails \u2192 try WebSearch or mcp__BrightData__scrape_as_markdown
+   - Example: If WebFetch fails \u2192 try mcp__BrightData__scrape_as_markdown
+3. **Try different strategies**: Break down the task or use alternative approaches
+4. **Only give up after exhausting options**: Report failure to user only when all reasonable alternatives have been tried
+
+Never tell the user "I cannot do this" after a single tool failure if alternative tools are available.
+
+- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are NOT part of the user's provided input or the tool result.`;
+}
+export {
+  getToolUsagePolicyPrompt
+};
+//# sourceMappingURL=toolUsagePolicy.js.map