@within-7/minto 0.4.1 → 0.4.2

package/dist/components/permissions/PlanApprovalRequest.js

@@ -0,0 +1,164 @@
+import { Box, Text, useInput } from "ink";
+import React, { useState } from "react";
+import InkTextInput from "ink-text-input";
+import { Select } from "../CustomSelect/select.js";
+import { getTheme } from "../../utils/theme.js";
+import { PermissionRequestTitle } from "./PermissionRequestTitle.js";
+import { BRAND_GRADIENT, SEMANTIC_COLORS } from "../../constants/colors.js";
+function PlanApprovalRequest({
+  toolUseConfirm,
+  onDone
+}) {
+  const theme = getTheme();
+  const planContent = toolUseConfirm.input?.planContent || "No plan content available";
+  const [mode, setMode] = useState("select");
+  const [feedback, setFeedback] = useState("");
+  const [promptsInput, setPromptsInput] = useState("");
+  useInput(
+    (input, key) => {
+      if (key.ctrl && input === "c") {
+        onDone();
+        toolUseConfirm.onAbort();
+        return;
+      }
+      if (key.escape && (mode === "feedback" || mode === "prompts")) {
+        setMode("select");
+        setFeedback("");
+        setPromptsInput("");
+      }
+    },
+    { isActive: true }
+  );
+  if (mode === "prompts") {
+    return /* @__PURE__ */ React.createElement(
+      Box,
+      {
+        flexDirection: "column",
+        borderStyle: "round",
+        borderColor: theme.permission,
+        marginTop: 1,
+        paddingLeft: 1,
+        paddingRight: 1,
+        paddingBottom: 1
+      },
+      /* @__PURE__ */ React.createElement(PermissionRequestTitle, { title: "Permitted Commands", riskScore: null }),
+      /* @__PURE__ */ React.createElement(Box, { flexDirection: "column", paddingX: 2, paddingY: 1 }, /* @__PURE__ */ React.createElement(Text, { color: theme.secondaryText }, "Enter comma-separated command patterns to auto-approve during plan execution:"), /* @__PURE__ */ React.createElement(Text, { color: SEMANTIC_COLORS.dim }, "Example: bun test, bun run typecheck, git *")),
+      /* @__PURE__ */ React.createElement(Box, { paddingX: 2 }, /* @__PURE__ */ React.createElement(Text, { color: BRAND_GRADIENT.START }, "> "), /* @__PURE__ */ React.createElement(
+        InkTextInput,
+        {
+          value: promptsInput,
+          onChange: setPromptsInput,
+          onSubmit: () => {
+            const trimmed = promptsInput.trim();
+            if (trimmed) {
+              const patterns = trimmed.split(",").map((p) => p.trim()).filter((p) => p.length > 0);
+              if (patterns.length > 0 && toolUseConfirm.onAllowWithPrompts) {
+                toolUseConfirm.onAllowWithPrompts(patterns);
+                onDone();
+              } else {
+                toolUseConfirm.onAllow("temporary");
+                onDone();
+              }
+            }
+          }
+        }
+      )),
+      /* @__PURE__ */ React.createElement(Box, { paddingX: 2, marginTop: 1 }, /* @__PURE__ */ React.createElement(Text, { color: SEMANTIC_COLORS.dim }, "Enter to submit, Esc to go back"))
+    );
+  }
+  if (mode === "feedback") {
+    return /* @__PURE__ */ React.createElement(
+      Box,
+      {
+        flexDirection: "column",
+        borderStyle: "round",
+        borderColor: theme.permission,
+        marginTop: 1,
+        paddingLeft: 1,
+        paddingRight: 1,
+        paddingBottom: 1
+      },
+      /* @__PURE__ */ React.createElement(PermissionRequestTitle, { title: "Plan Feedback", riskScore: null }),
+      /* @__PURE__ */ React.createElement(Box, { flexDirection: "column", paddingX: 2, paddingY: 1 }, /* @__PURE__ */ React.createElement(Text, { color: theme.secondaryText }, "Provide feedback for plan revision (Esc to go back):")),
+      /* @__PURE__ */ React.createElement(Box, { paddingX: 2 }, /* @__PURE__ */ React.createElement(Text, { color: BRAND_GRADIENT.START }, "> "), /* @__PURE__ */ React.createElement(
+        InkTextInput,
+        {
+          value: feedback,
+          onChange: setFeedback,
+          onSubmit: () => {
+            if (feedback.trim()) {
+              if (toolUseConfirm.onRejectWithFeedback) {
+                toolUseConfirm.onRejectWithFeedback(feedback.trim());
+              } else {
+                toolUseConfirm.onReject();
+              }
+              onDone();
+            }
+          }
+        }
+      )),
+      /* @__PURE__ */ React.createElement(Box, { paddingX: 2, marginTop: 1 }, /* @__PURE__ */ React.createElement(Text, { color: SEMANTIC_COLORS.dim }, "Enter to submit, Esc to go back"))
+    );
+  }
+  const truncatedPlan = planContent.length > 500 ? planContent.substring(0, 500) + "..." : planContent;
+  return /* @__PURE__ */ React.createElement(
+    Box,
+    {
+      flexDirection: "column",
+      borderStyle: "round",
+      borderColor: theme.permission,
+      marginTop: 1,
+      paddingLeft: 1,
+      paddingRight: 1,
+      paddingBottom: 1
+    },
+    /* @__PURE__ */ React.createElement(PermissionRequestTitle, { title: "Plan Approval", riskScore: null }),
+    /* @__PURE__ */ React.createElement(Box, { flexDirection: "column", paddingX: 2, paddingY: 1 }, /* @__PURE__ */ React.createElement(Text, { bold: true }, "Review plan:"), /* @__PURE__ */ React.createElement(
+      Box,
+      {
+        borderStyle: "round",
+        borderColor: "cyan",
+        borderDimColor: true,
+        paddingX: 1,
+        marginY: 1
+      },
+      /* @__PURE__ */ React.createElement(Text, { color: SEMANTIC_COLORS.dim }, truncatedPlan)
+    )),
+    /* @__PURE__ */ React.createElement(Box, { flexDirection: "column" }, /* @__PURE__ */ React.createElement(Text, null, "Choose an action:"), /* @__PURE__ */ React.createElement(
+      Select,
+      {
+        options: [
+          { label: "Approve plan", value: "approve" },
+          {
+            label: "Approve with permitted commands",
+            value: "approve-prompts"
+          },
+          { label: "Reject with feedback", value: "reject-feedback" },
+          { label: "Cancel (esc)", value: "cancel" }
+        ],
+        onChange: (value) => {
+          switch (value) {
+            case "approve":
+              toolUseConfirm.onAllow("temporary");
+              onDone();
+              break;
+            case "approve-prompts":
+              setMode("prompts");
+              break;
+            case "reject-feedback":
+              setMode("feedback");
+              break;
+            case "cancel":
+              toolUseConfirm.onAbort();
+              onDone();
+              break;
+          }
+        }
+      }
+    ))
+  );
+}
+export {
+  PlanApprovalRequest
+};
+//# sourceMappingURL=PlanApprovalRequest.js.map

package/dist/components/permissions/PlanApprovalRequest.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/components/permissions/PlanApprovalRequest.tsx"],
+  "sourcesContent": ["import { Box, Text, useInput } from 'ink'\nimport React, { useState } from 'react'\nimport InkTextInput from 'ink-text-input'\nimport { Select } from '@components/CustomSelect/select'\nimport { getTheme } from '@utils/theme'\nimport { PermissionRequestTitle } from './PermissionRequestTitle'\nimport { type ToolUseConfirm } from './PermissionRequest'\nimport { BRAND_GRADIENT, SEMANTIC_COLORS } from '@constants/colors'\n\ntype Props = {\n  toolUseConfirm: ToolUseConfirm\n  onDone(): void\n  verbose: boolean\n}\n\nexport function PlanApprovalRequest({\n  toolUseConfirm,\n  onDone,\n}: Props): React.ReactNode {\n  const theme = getTheme()\n  const planContent =\n    (toolUseConfirm.input as any)?.planContent || 'No plan content available'\n  const [mode, setMode] = useState<'select' | 'feedback' | 'prompts'>('select')\n  const [feedback, setFeedback] = useState('')\n  const [promptsInput, setPromptsInput] = useState('')\n\n  // Handle Ctrl+C and Escape in both modes\n  useInput(\n    (input, key) => {\n      if (key.ctrl && input === 'c') {\n        onDone()\n        toolUseConfirm.onAbort()\n        return\n      }\n      if (key.escape && (mode === 'feedback' || mode === 'prompts')) {\n        setMode('select')\n        setFeedback('')\n        setPromptsInput('')\n      }\n    },\n    { isActive: true },\n  )\n\n  if (mode === 'prompts') {\n    return (\n      <Box\n        flexDirection=\"column\"\n        borderStyle=\"round\"\n        borderColor={theme.permission}\n        marginTop={1}\n        paddingLeft={1}\n        paddingRight={1}\n        paddingBottom={1}\n      >\n        <PermissionRequestTitle title=\"Permitted Commands\" riskScore={null} />\n        <Box flexDirection=\"column\" paddingX={2} paddingY={1}>\n          <Text color={theme.secondaryText}>\n            Enter comma-separated command patterns to auto-approve during plan\n            execution:\n          </Text>\n          <Text color={SEMANTIC_COLORS.dim}>\n            Example: bun test, bun run typecheck, git *\n          </Text>\n        </Box>\n        <Box paddingX={2}>\n          <Text color={BRAND_GRADIENT.START}>&gt; </Text>\n          <InkTextInput\n            value={promptsInput}\n            onChange={setPromptsInput}\n            onSubmit={() => {\n              const trimmed = promptsInput.trim()\n              if (trimmed) {\n                const patterns = trimmed\n                  .split(',')\n                  .map(p => p.trim())\n                  .filter(p => p.length > 0)\n                if (patterns.length > 0 && toolUseConfirm.onAllowWithPrompts) {\n                  toolUseConfirm.onAllowWithPrompts(patterns)\n                  onDone()\n                } else {\n                  // Fallback: approve without specific patterns\n                  toolUseConfirm.onAllow('temporary')\n                  onDone()\n                }\n              }\n            }}\n          />\n        </Box>\n        <Box paddingX={2} marginTop={1}>\n          <Text color={SEMANTIC_COLORS.dim}>\n            Enter to submit, Esc to go back\n          </Text>\n        </Box>\n      </Box>\n    )\n  }\n\n  if (mode === 'feedback') {\n    return (\n      <Box\n        flexDirection=\"column\"\n        borderStyle=\"round\"\n        borderColor={theme.permission}\n        marginTop={1}\n        paddingLeft={1}\n        paddingRight={1}\n        paddingBottom={1}\n      >\n        <PermissionRequestTitle title=\"Plan Feedback\" riskScore={null} />\n        <Box flexDirection=\"column\" paddingX={2} paddingY={1}>\n          <Text color={theme.secondaryText}>\n            Provide feedback for plan revision (Esc to go back):\n          </Text>\n        </Box>\n        <Box paddingX={2}>\n          <Text color={BRAND_GRADIENT.START}>&gt; </Text>\n          <InkTextInput\n            value={feedback}\n            onChange={setFeedback}\n            onSubmit={() => {\n              if (feedback.trim()) {\n                if (toolUseConfirm.onRejectWithFeedback) {\n                  toolUseConfirm.onRejectWithFeedback(feedback.trim())\n                } else {\n                  toolUseConfirm.onReject()\n                }\n                onDone()\n              }\n            }}\n          />\n        </Box>\n        <Box paddingX={2} marginTop={1}>\n          <Text color={SEMANTIC_COLORS.dim}>\n            Enter to submit, Esc to go back\n          </Text>\n        </Box>\n      </Box>\n    )\n  }\n\n  // Truncate plan for display (first 500 chars)\n  const truncatedPlan =\n    planContent.length > 500\n      ? planContent.substring(0, 500) + '...'\n      : planContent\n\n  return (\n    <Box\n      flexDirection=\"column\"\n      borderStyle=\"round\"\n      borderColor={theme.permission}\n      marginTop={1}\n      paddingLeft={1}\n      paddingRight={1}\n      paddingBottom={1}\n    >\n      <PermissionRequestTitle title=\"Plan Approval\" riskScore={null} />\n      <Box flexDirection=\"column\" paddingX={2} paddingY={1}>\n        <Text bold>Review plan:</Text>\n        <Box\n          borderStyle=\"round\"\n          borderColor=\"cyan\"\n          borderDimColor\n          paddingX={1}\n          marginY={1}\n        >\n          <Text color={SEMANTIC_COLORS.dim}>{truncatedPlan}</Text>\n        </Box>\n      </Box>\n      <Box flexDirection=\"column\">\n        <Text>Choose an action:</Text>\n        <Select\n          options={[\n            { label: 'Approve plan', value: 'approve' },\n            {\n              label: 'Approve with permitted commands',\n              value: 'approve-prompts',\n            },\n            { label: 'Reject with feedback', value: 'reject-feedback' },\n            { label: 'Cancel (esc)', value: 'cancel' },\n          ]}\n          onChange={value => {\n            switch (value) {\n              case 'approve':\n                toolUseConfirm.onAllow('temporary')\n                onDone()\n                break\n              case 'approve-prompts':\n                setMode('prompts')\n                break\n              case 'reject-feedback':\n                setMode('feedback')\n                break\n              case 'cancel':\n                toolUseConfirm.onAbort()\n                onDone()\n                break\n            }\n          }}\n        />\n      </Box>\n    </Box>\n  )\n}\n"],
+  "mappings": "AAAA,SAAS,KAAK,MAAM,gBAAgB;AACpC,OAAO,SAAS,gBAAgB;AAChC,OAAO,kBAAkB;AACzB,SAAS,cAAc;AACvB,SAAS,gBAAgB;AACzB,SAAS,8BAA8B;AAEvC,SAAS,gBAAgB,uBAAuB;AAQzC,SAAS,oBAAoB;AAAA,EAClC;AAAA,EACA;AACF,GAA2B;AACzB,QAAM,QAAQ,SAAS;AACvB,QAAM,cACH,eAAe,OAAe,eAAe;AAChD,QAAM,CAAC,MAAM,OAAO,IAAI,SAA4C,QAAQ;AAC5E,QAAM,CAAC,UAAU,WAAW,IAAI,SAAS,EAAE;AAC3C,QAAM,CAAC,cAAc,eAAe,IAAI,SAAS,EAAE;AAGnD;AAAA,IACE,CAAC,OAAO,QAAQ;AACd,UAAI,IAAI,QAAQ,UAAU,KAAK;AAC7B,eAAO;AACP,uBAAe,QAAQ;AACvB;AAAA,MACF;AACA,UAAI,IAAI,WAAW,SAAS,cAAc,SAAS,YAAY;AAC7D,gBAAQ,QAAQ;AAChB,oBAAY,EAAE;AACd,wBAAgB,EAAE;AAAA,MACpB;AAAA,IACF;AAAA,IACA,EAAE,UAAU,KAAK;AAAA,EACnB;AAEA,MAAI,SAAS,WAAW;AACtB,WACE;AAAA,MAAC;AAAA;AAAA,QACC,eAAc;AAAA,QACd,aAAY;AAAA,QACZ,aAAa,MAAM;AAAA,QACnB,WAAW;AAAA,QACX,aAAa;AAAA,QACb,cAAc;AAAA,QACd,eAAe;AAAA;AAAA,MAEf,oCAAC,0BAAuB,OAAM,sBAAqB,WAAW,MAAM;AAAA,MACpE,oCAAC,OAAI,eAAc,UAAS,UAAU,GAAG,UAAU,KACjD,oCAAC,QAAK,OAAO,MAAM,iBAAe,+EAGlC,GACA,oCAAC,QAAK,OAAO,gBAAgB,OAAK,6CAElC,CACF;AAAA,MACA,oCAAC,OAAI,UAAU,KACb,oCAAC,QAAK,OAAO,eAAe,SAAO,IAAK,GACxC;AAAA,QAAC;AAAA;AAAA,UACC,OAAO;AAAA,UACP,UAAU;AAAA,UACV,UAAU,MAAM;AACd,kBAAM,UAAU,aAAa,KAAK;AAClC,gBAAI,SAAS;AACX,oBAAM,WAAW,QACd,MAAM,GAAG,EACT,IAAI,OAAK,EAAE,KAAK,CAAC,EACjB,OAAO,OAAK,EAAE,SAAS,CAAC;AAC3B,kBAAI,SAAS,SAAS,KAAK,eAAe,oBAAoB;AAC5D,+BAAe,mBAAmB,QAAQ;AAC1C,uBAAO;AAAA,cACT,OAAO;AAEL,+BAAe,QAAQ,WAAW;AAClC,uBAAO;AAAA,cACT;AAAA,YACF;AAAA,UACF;AAAA;AAAA,MACF,CACF;AAAA,MACA,oCAAC,OAAI,UAAU,GAAG,WAAW,KAC3B,oCAAC,QAAK,OAAO,gBAAgB,OAAK,iCAElC,CACF;AAAA,IACF;AAAA,EAEJ;AAEA,MAAI,SAAS,YAAY;AACvB,WACE;AAAA,MAAC;AAAA;AAAA,QACC,eAAc;AAAA,QACd,aAAY;AAAA,QACZ,aAAa,MAAM;AAAA,QACnB,WAAW;AAAA,QACX,aAAa;AAAA,QACb,cAAc;AAAA,QACd,eAAe;AAAA;AAAA,MAEf,oCAAC,0BAAuB,OAAM,iBAAgB,WAAW,MAAM;AAAA,MAC/D,oCAAC,OAAI,eAAc,UAAS,UAAU,GAAG,UAAU,KACjD,oCAAC,QAAK,OAAO,MAAM,iBAAe,sDAElC,CACF;AAAA,MACA,oCAAC,OAAI,UAAU,KACb,oCAAC,QAAK,OAAO,eAAe,SAAO,IAAK,GACxC;AAAA,QAAC;AAAA;AAAA,UACC,OAAO;AAAA,UACP,UAAU;AAAA,UACV,UAAU,MAAM;AACd,gBAAI,SAAS,KAAK,GAAG;AACnB,kBAAI,eAAe,sBAAsB;AACvC,+BAAe,qBAAqB,SAAS,KAAK,CAAC;AAAA,cACrD,OAAO;AACL,+BAAe,SAAS;AAAA,cAC1B;AACA,qBAAO;AAAA,YACT;AAAA,UACF;AAAA;AAAA,MACF,CACF;AAAA,MACA,oCAAC,OAAI,UAAU,GAAG,WAAW,KAC3B,oCAAC,QAAK,OAAO,gBAAgB,OAAK,iCAElC,CACF;AAAA,IACF;AAAA,EAEJ;AAGA,QAAM,gBACJ,YAAY,SAAS,MACjB,YAAY,UAAU,GAAG,GAAG,IAAI,QAChC;AAEN,SACE;AAAA,IAAC;AAAA;AAAA,MACC,eAAc;AAAA,MACd,aAAY;AAAA,MACZ,aAAa,MAAM;AAAA,MACnB,WAAW;AAAA,MACX,aAAa;AAAA,MACb,cAAc;AAAA,MACd,eAAe;AAAA;AAAA,IAEf,oCAAC,0BAAuB,OAAM,iBAAgB,WAAW,MAAM;AAAA,IAC/D,oCAAC,OAAI,eAAc,UAAS,UAAU,GAAG,UAAU,KACjD,oCAAC,QAAK,MAAI,QAAC,cAAY,GACvB;AAAA,MAAC;AAAA;AAAA,QACC,aAAY;AAAA,QACZ,aAAY;AAAA,QACZ,gBAAc;AAAA,QACd,UAAU;AAAA,QACV,SAAS;AAAA;AAAA,MAET,oCAAC,QAAK,OAAO,gBAAgB,OAAM,aAAc;AAAA,IACnD,CACF;AAAA,IACA,oCAAC,OAAI,eAAc,YACjB,oCAAC,YAAK,mBAAiB,GACvB;AAAA,MAAC;AAAA;AAAA,QACC,SAAS;AAAA,UACP,EAAE,OAAO,gBAAgB,OAAO,UAAU;AAAA,UAC1C;AAAA,YACE,OAAO;AAAA,YACP,OAAO;AAAA,UACT;AAAA,UACA,EAAE,OAAO,wBAAwB,OAAO,kBAAkB;AAAA,UAC1D,EAAE,OAAO,gBAAgB,OAAO,SAAS;AAAA,QAC3C;AAAA,QACA,UAAU,WAAS;AACjB,kBAAQ,OAAO;AAAA,YACb,KAAK;AACH,6BAAe,QAAQ,WAAW;AAClC,qBAAO;AACP;AAAA,YACF,KAAK;AACH,sBAAQ,SAAS;AACjB;AAAA,YACF,KAAK;AACH,sBAAQ,UAAU;AAClB;AAAA,YACF,KAAK;AACH,6BAAe,QAAQ;AACvB,qBAAO;AACP;AAAA,UACJ;AAAA,QACF;AAAA;AAAA,IACF,CACF;AAAA,EACF;AAEJ;",
+  "names": []
+}

package/dist/constants/agentTeams.js

@@ -0,0 +1,17 @@
+const TEAMMATE_COLORS = [
+  "cyan",
+  "magenta",
+  "yellow",
+  "green",
+  "blue",
+  "red",
+  "white"
+];
+function getTeammateColor(index) {
+  return TEAMMATE_COLORS[index % TEAMMATE_COLORS.length];
+}
+export {
+  TEAMMATE_COLORS,
+  getTeammateColor
+};
+//# sourceMappingURL=agentTeams.js.map

package/dist/constants/agentTeams.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../src/constants/agentTeams.ts"],
+  "sourcesContent": ["/**\n * Shared constants for Agent Teams\n */\n\n/**\n * Teammate colors for UI differentiation.\n * Used by both TaskTool (in-process registration) and teammateSpawner.\n */\nexport const TEAMMATE_COLORS = [\n  'cyan',\n  'magenta',\n  'yellow',\n  'green',\n  'blue',\n  'red',\n  'white',\n]\n\n/**\n * Get the color for a teammate by index (cycles through TEAMMATE_COLORS).\n */\nexport function getTeammateColor(index: number): string {\n  return TEAMMATE_COLORS[index % TEAMMATE_COLORS.length]!\n}\n"],
+  "mappings": "AAQO,MAAM,kBAAkB;AAAA,EAC7B;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAKO,SAAS,iBAAiB,OAAuB;AACtD,SAAO,gBAAgB,QAAQ,gBAAgB,MAAM;AACvD;",
+  "names": []
+}

package/dist/constants/macros.js

@@ -3,7 +3,8 @@ const MACRO = {
   VERSION,
   README_URL: "https://minto.within-7.com/",
   PACKAGE_URL: "@within-7/minto",
-  ISSUES_EXPLAINER: "report the issue to within-7 team"
+  ISSUES_EXPLAINER: "report the issue to within-7 team",
+  LOGIN_API_URL: "https://api.within-7.com/user/login"
 };
 export {
   MACRO

package/dist/constants/macros.js.map

@@ -1,7 +1,7 @@
 {
   "version": 3,
   "sources": ["../../src/constants/macros.ts"],
-  "sourcesContent": ["import { VERSION } from '../version.js'\n\nexport const MACRO = {\n  VERSION: VERSION,\n  README_URL: 'https://minto.within-7.com/',\n  PACKAGE_URL: '@within-7/minto',\n  ISSUES_EXPLAINER: 'report the issue to within-7 team',\n}\n"],
-  "mappings": "AAAA,SAAS,eAAe;AAEjB,MAAM,QAAQ;AAAA,EACnB;AAAA,EACA,YAAY;AAAA,EACZ,aAAa;AAAA,EACb,kBAAkB;AACpB;",
+  "sourcesContent": ["import { VERSION } from '../version.js'\n\nexport const MACRO = {\n  VERSION: VERSION,\n  README_URL: 'https://minto.within-7.com/',\n  PACKAGE_URL: '@within-7/minto',\n  ISSUES_EXPLAINER: 'report the issue to within-7 team',\n  LOGIN_API_URL: 'https://api.within-7.com/user/login',\n}\n"],
+  "mappings": "AAAA,SAAS,eAAe;AAEjB,MAAM,QAAQ;AAAA,EACnB;AAAA,EACA,YAAY;AAAA,EACZ,aAAa;AAAA,EACb,kBAAkB;AAAA,EAClB,eAAe;AACjB;",
   "names": []
 }

package/dist/constants/prompts/agentPrompt.js

@@ -11,6 +11,7 @@ Your strengths:
 - Performing multi-step research tasks
 
 Guidelines:
+- All operations should be scoped to the current working directory (project) unless explicitly instructed otherwise. When asked to find, search, or analyze files, always search within the project directory, not the entire filesystem.
 - 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.

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

@@ -1,7 +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;",
+  "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- All operations should be scoped to the current working directory (project) unless explicitly instructed otherwise. When asked to find, search, or analyze files, always search within the project directory, not the entire filesystem.\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;AAAA,IAoBpC,GAAG,MAAM,iBAAiB,CAAC;AAAA,EAC7B;AACF;",
   "names": []
 }

package/dist/constants/prompts/autoMemory.js

@@ -0,0 +1,39 @@
+import { getAutoMemoryDir } from "../../utils/autoMemoryPaths.js";
+function getAutoMemoryPrompt() {
+  const memoryDir = getAutoMemoryDir();
+  return `# auto memory
+
+You have a persistent auto memory directory at \`${memoryDir}\`. Its contents persist across conversations.
+
+As you work, consult your memory files to build on previous experience.
+
+## How to save memories:
+- Organize memory semantically by topic, not chronologically
+- Use the Write and Edit tools to update your memory files
+- \`MEMORY.md\` is always loaded into your conversation context \u2014 lines after 200 will be truncated, so keep it concise
+- Create separate topic files (e.g., \`debugging.md\`, \`patterns.md\`) for detailed notes and link to them from MEMORY.md
+- Update or remove memories that turn out to be wrong or outdated
+- Do not write duplicate memories. First check if there is an existing memory you can update before writing a new one.
+
+## What to save:
+- Stable patterns and conventions confirmed across multiple interactions
+- Key architectural decisions, important file paths, and project structure
+- User preferences for workflow, tools, and communication style
+- Solutions to recurring problems and debugging insights
+
+## What NOT to save:
+- Session-specific context (current task details, in-progress work, temporary state)
+- Information that might be incomplete \u2014 verify against project docs before writing
+- Anything that duplicates or contradicts existing CLAUDE.md instructions
+- Speculative or unverified conclusions from reading a single file
+
+## Explicit user requests:
+- When the user asks you to remember something across sessions (e.g., "always use bun", "never auto-commit"), save it \u2014 no need to wait for multiple interactions
+- When the user asks to forget or stop remembering something, find and remove the relevant entries from your memory files
+- When the user corrects you on something you stated from memory, you MUST update or remove the incorrect entry. A correction means the stored memory is wrong \u2014 fix it at the source before continuing, so the same mistake does not repeat in future conversations.
+`;
+}
+export {
+  getAutoMemoryPrompt
+};
+//# sourceMappingURL=autoMemory.js.map

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

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/constants/prompts/autoMemory.ts"],
+  "sourcesContent": ["/**\n * Auto Memory system prompt block.\n *\n * CC-compatible implementation: instructs the LLM to manage its own\n * persistent memory files using standard Read/Write/Edit tools.\n *\n * Memory directory: ~/.minto/projects/<project-slug>/memory/\n * Index file: MEMORY.md (first 200 lines loaded into every session)\n * Topic files: e.g. debugging.md, patterns.md (linked from MEMORY.md)\n */\n\nimport { getAutoMemoryDir } from '@utils/autoMemoryPaths'\n\nexport function getAutoMemoryPrompt(): string {\n  const memoryDir = getAutoMemoryDir()\n\n  return `# auto memory\n\nYou have a persistent auto memory directory at \\`${memoryDir}\\`. Its contents persist across conversations.\n\nAs you work, consult your memory files to build on previous experience.\n\n## How to save memories:\n- Organize memory semantically by topic, not chronologically\n- Use the Write and Edit tools to update your memory files\n- \\`MEMORY.md\\` is always loaded into your conversation context \u2014 lines after 200 will be truncated, so keep it concise\n- Create separate topic files (e.g., \\`debugging.md\\`, \\`patterns.md\\`) for detailed notes and link to them from MEMORY.md\n- Update or remove memories that turn out to be wrong or outdated\n- Do not write duplicate memories. First check if there is an existing memory you can update before writing a new one.\n\n## What to save:\n- Stable patterns and conventions confirmed across multiple interactions\n- Key architectural decisions, important file paths, and project structure\n- User preferences for workflow, tools, and communication style\n- Solutions to recurring problems and debugging insights\n\n## What NOT to save:\n- Session-specific context (current task details, in-progress work, temporary state)\n- Information that might be incomplete \u2014 verify against project docs before writing\n- Anything that duplicates or contradicts existing CLAUDE.md instructions\n- Speculative or unverified conclusions from reading a single file\n\n## Explicit user requests:\n- When the user asks you to remember something across sessions (e.g., \"always use bun\", \"never auto-commit\"), save it \u2014 no need to wait for multiple interactions\n- When the user asks to forget or stop remembering something, find and remove the relevant entries from your memory files\n- When the user corrects you on something you stated from memory, you MUST update or remove the incorrect entry. A correction means the stored memory is wrong \u2014 fix it at the source before continuing, so the same mistake does not repeat in future conversations.\n`\n}\n"],
+  "mappings": "AAWA,SAAS,wBAAwB;AAE1B,SAAS,sBAA8B;AAC5C,QAAM,YAAY,iBAAiB;AAEnC,SAAO;AAAA;AAAA,mDAE0C,SAAS;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;AA6B5D;",
+  "names": []
+}

package/dist/constants/prompts/codeConventions.js

@@ -7,19 +7,7 @@ When making changes to files, first understand the file's code conventions. Mimi
 - 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`;
+- Do not add comments to the code you write, unless the user asks you to, or the code is complex and requires additional context.`;
 }
 export {
   getCodeConventionsPrompt

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

@@ -1,7 +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;",
+  "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"],
+  "mappings": "AAAO,SAAS,2BAAmC;AACjD,SAAO;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAST;",
   "names": []
 }

package/dist/constants/prompts/doingTasks.js

@@ -1,13 +1,32 @@
 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:
+ - The user will primarily request you to perform software engineering tasks. These may include solving bugs, adding new functionality, refactoring code, explaining code, and more. When given an unclear or generic instruction, consider it in the context of these software engineering tasks and the current working directory. For example, if the user asks you to change "methodName" to snake case, do not reply with just "method_name", instead find the method in the code and modify the code.
+ - You are highly capable and often allow users to complete ambitious tasks that would otherwise be too complex or take too long. You should defer to user judgement about whether a task is too large to attempt.
+ - In general, do not propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.
+ - Do not create files unless they're absolutely necessary for achieving your goal. Generally prefer editing an existing file to creating a new one, as this prevents file bloat and builds on existing work more effectively.
+ - Avoid giving time estimates or predictions for how long tasks will take, whether for your own work or for users planning projects. Focus on what needs to be done, not how long it might take.
+ - If your approach is blocked, do not attempt to brute force your way to the outcome. For example, if an API call or test fails, do not wait and retry the same action repeatedly. Instead, consider alternative approaches or other ways you might unblock yourself, or consider using the AskUserQuestion to align with the user on the right path forward.
+ - Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it. Prioritize writing safe, secure, and correct code.
+ - Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.
+  - Don't add features, refactor code, or make "improvements" beyond what was asked. A bug fix doesn't need surrounding code cleaned up. A simple feature doesn't need extra configurability. Don't add docstrings, comments, or type annotations to code you didn't change. Only add comments where the logic isn't self-evident.
+  - Don't add error handling, fallbacks, or validation for scenarios that can't happen. Trust internal code and framework guarantees. Only validate at system boundaries (user input, external APIs). Don't use feature flags or backwards-compatibility shims when you can just change the code.
+  - Don't create helpers, utilities, or abstractions for one-time operations. Don't design for hypothetical future requirements. The right amount of complexity is the minimum needed for the current task\u2014three similar lines of code is better than a premature abstraction.
+ - Avoid backwards-compatibility hacks like renaming unused _vars, re-exporting types, adding // removed comments for removed code, etc. If you are certain that something is unused, you can delete it completely.
+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.`;
+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.
+
+# Real-time user guidance
+The user can inject guidance while you are working by typing messages during your response. These appear as \`<user-guidance>\` tags in the conversation. When you see a \`<user-guidance>\` message:
+ - You MUST acknowledge the guidance explicitly in your next response
+ - Adjust your current plan to follow the guidance immediately
+ - If the guidance conflicts with actions already completed, explain what was already done and offer to redo if needed
+ - Never silently ignore user guidance \u2014 the user is actively steering your behavior`;
 }
 export {
   getDoingTasksPrompt

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

@@ -1,7 +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;",
+  "sourcesContent": ["import { PRODUCT_NAME, PROJECT_FILE } from '../product'\nimport { BashTool } from '@tools/BashTool/BashTool'\n\nexport function getDoingTasksPrompt(): string {\n  return `# Doing tasks\n - The user will primarily request you to perform software engineering tasks. These may include solving bugs, adding new functionality, refactoring code, explaining code, and more. When given an unclear or generic instruction, consider it in the context of these software engineering tasks and the current working directory. For example, if the user asks you to change \"methodName\" to snake case, do not reply with just \"method_name\", instead find the method in the code and modify the code.\n - You are highly capable and often allow users to complete ambitious tasks that would otherwise be too complex or take too long. You should defer to user judgement about whether a task is too large to attempt.\n - In general, do not propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.\n - Do not create files unless they're absolutely necessary for achieving your goal. Generally prefer editing an existing file to creating a new one, as this prevents file bloat and builds on existing work more effectively.\n - Avoid giving time estimates or predictions for how long tasks will take, whether for your own work or for users planning projects. Focus on what needs to be done, not how long it might take.\n - If your approach is blocked, do not attempt to brute force your way to the outcome. For example, if an API call or test fails, do not wait and retry the same action repeatedly. Instead, consider alternative approaches or other ways you might unblock yourself, or consider using the AskUserQuestion to align with the user on the right path forward.\n - Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it. Prioritize writing safe, secure, and correct code.\n - Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.\n  - Don't add features, refactor code, or make \"improvements\" beyond what was asked. A bug fix doesn't need surrounding code cleaned up. A simple feature doesn't need extra configurability. Don't add docstrings, comments, or type annotations to code you didn't change. Only add comments where the logic isn't self-evident.\n  - Don't add error handling, fallbacks, or validation for scenarios that can't happen. Trust internal code and framework guarantees. Only validate at system boundaries (user input, external APIs). Don't use feature flags or backwards-compatibility shims when you can just change the code.\n  - Don't create helpers, utilities, or abstractions for one-time operations. Don't design for hypothetical future requirements. The right amount of complexity is the minimum needed for the current task\u2014three similar lines of code is better than a premature abstraction.\n - Avoid backwards-compatibility hacks like renaming unused _vars, re-exporting types, adding // removed comments for removed code, etc. If you are certain that something is unused, you can delete it completely.\nFor 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# Real-time user guidance\nThe user can inject guidance while you are working by typing messages during your response. These appear as \\`<user-guidance>\\` tags in the conversation. When you see a \\`<user-guidance>\\` message:\n - You MUST acknowledge the guidance explicitly in your next response\n - Adjust your current plan to follow the guidance immediately\n - If the guidance conflicts with actions already completed, explain what was already done and offer to redo if needed\n - Never silently ignore user guidance \u2014 the user is actively steering your behavior`\n}\n"],
+  "mappings": "AAAA,SAAuB,oBAAoB;AAGpC,SAAS,sBAA8B;AAC5C,SAAO;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,4VAkBmV,YAAY;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AASxW;",
   "names": []
 }

package/dist/constants/prompts/envInfo.js

@@ -3,13 +3,12 @@ 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>`;
+  return `# Environment
+You have been invoked in the following environment:
+ - Primary working directory: ${getCwd()}
+  - Is a git repository: ${isGit ? "Yes" : "No"}
+ - Platform: ${env.platform}
+ - Today's date: ${(/* @__PURE__ */ new Date()).toISOString().split("T")[0]}`;
 }
 export {
   getEnvInfoPrompt

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

@@ -1,7 +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;",
+  "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 `# Environment\nYou have been invoked in the following environment:\n - Primary working directory: ${getCwd()}\n  - Is a git repository: ${isGit ? 'Yes' : 'No'}\n - Platform: ${env.platform}\n - Today's date: ${new Date().toISOString().split('T')[0]}`\n}\n"],
+  "mappings": "AAAA,SAAS,WAAW;AACpB,SAAS,gBAAgB;AACzB,SAAS,cAAc;AAEvB,eAAsB,mBAAoC;AACxD,QAAM,QAAQ,MAAM,SAAS;AAC7B,SAAO;AAAA;AAAA,gCAEuB,OAAO,CAAC;AAAA,2BACb,QAAQ,QAAQ,IAAI;AAAA,eAChC,IAAI,QAAQ;AAAA,oBACR,oBAAI,KAAK,GAAE,YAAY,EAAE,MAAM,GAAG,EAAE,CAAC,CAAC;AACzD;",
   "names": []
 }

package/dist/constants/prompts/index.js

@@ -6,7 +6,10 @@ import { getToolUsagePolicyPrompt } from "./toolUsagePolicy.js";
 import { getTaskManagementPrompt } from "./taskManagement.js";
 import { getCodeConventionsPrompt } from "./codeConventions.js";
 import { getEnvInfoPrompt } from "./envInfo.js";
+import { getAutoMemoryPrompt } from "./autoMemory.js";
 import { emitReminderEvent } from "../../services/systemReminder.js";
+import { getTeamLeadOverlay, getTeammateOverlay } from "./teamOverlays.js";
+import { isAutoMemoryEnabled } from "../../utils/autoMemoryPaths.js";
 import { getAgentPrompt } from "./agentPrompt.js";
 import { getEnvInfoPrompt as getEnvInfoPrompt2 } from "./envInfo.js";
 import { PRODUCT_NAME } from "../product.js";
@@ -35,7 +38,7 @@ ${styleDescriptions}`;
     return null;
   }
 }
-async function getSystemPrompt() {
+async function getSystemPrompt(role) {
   const blocks = [];
   let keepCoding = true;
   try {
@@ -55,15 +58,34 @@ async function getSystemPrompt() {
     blocks.push(getDoingTasksPrompt());
   }
   blocks.push(getToolUsagePolicyPrompt());
+  if (keepCoding) {
+    blocks.push(
+      `# Output efficiency
+
+IMPORTANT: Go straight to the point. Try the simplest approach first without going in circles. Do not overdo it. Be extra concise.
+
+Keep your text output brief and direct. Lead with the answer or action, not the reasoning. Skip filler words, preamble, and unnecessary transitions. Do not restate what the user said \u2014 just do it. When explaining, include only what is necessary for the user to understand.
+
+Focus text output on:
+- Decisions that need the user's input
+- High-level status updates at natural milestones
+- Errors or blockers that change the plan
+
+If you can say it in one sentence, don't use three. Prefer short, direct sentences over long explanations. This does not apply to code or tool calls.`
+    );
+  }
   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.`
-    );
+  if (role === "team-lead") {
+    blocks.push(getTeamLeadOverlay());
+  } else if (role === "teammate") {
+    blocks.push(getTeammateOverlay());
+  }
+  if (isAutoMemoryEnabled()) {
+    blocks.push(getAutoMemoryPrompt());
   }
   blocks.push(`
 ${await getEnvInfoPrompt()}`);

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

@@ -1,7 +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;",
+  "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 { getAutoMemoryPrompt } from './autoMemory'\nimport { emitReminderEvent } from '@services/systemReminder'\nimport { getTeamLeadOverlay, getTeammateOverlay } from './teamOverlays'\nimport { isAutoMemoryEnabled } from '@utils/autoMemoryPaths'\nimport type { AgentRole } from '../../engine/types'\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(role?: AgentRole): 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  if (keepCoding) {\n    // Conciseness reminder \u2014 placed before outputStyle for cache stability\n    // (outputStyle is dynamic/conditional, conciseness is static)\n    blocks.push(\n      `# Output efficiency\n\nIMPORTANT: Go straight to the point. Try the simplest approach first without going in circles. Do not overdo it. Be extra concise.\n\nKeep your text output brief and direct. Lead with the answer or action, not the reasoning. Skip filler words, preamble, and unnecessary transitions. Do not restate what the user said \u2014 just do it. When explaining, include only what is necessary for the user to understand.\n\nFocus text output on:\n- Decisions that need the user's input\n- High-level status updates at natural milestones\n- Errors or blockers that change the plan\n\nIf you can say it in one sentence, don't use three. Prefer short, direct sentences over long explanations. This does not apply to code or tool calls.`,\n    )\n  }\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  // Role overlay \u2014 after outputStyle/conciseness, before envInfo\n  if (role === 'team-lead') {\n    blocks.push(getTeamLeadOverlay())\n  } else if (role === 'teammate') {\n    blocks.push(getTeammateOverlay())\n  }\n\n  // Auto memory (CC-compatible LLM-driven persistent memory)\n  if (isAutoMemoryEnabled()) {\n    blocks.push(getAutoMemoryPrompt())\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,2BAA2B;AACpC,SAAS,yBAAyB;AAClC,SAAS,oBAAoB,0BAA0B;AACvD,SAAS,2BAA2B;AAIpC,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,gBAAgB,MAAqC;AACzE,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;AAEtC,MAAI,YAAY;AAGd,WAAO;AAAA,MACL;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAYF;AAAA,EACF;AAGA,QAAM,mBAAmB,MAAM,qBAAqB;AACpD,MAAI,kBAAkB;AACpB,WAAO,KAAK,gBAAgB;AAC5B,sBAAkB,uBAAuB,EAAE,WAAW,SAAS,CAAC;AAAA,EAClE;AAGA,MAAI,SAAS,aAAa;AACxB,WAAO,KAAK,mBAAmB,CAAC;AAAA,EAClC,WAAW,SAAS,YAAY;AAC9B,WAAO,KAAK,mBAAmB,CAAC;AAAA,EAClC;AAGA,MAAI,oBAAoB,GAAG;AACzB,WAAO,KAAK,oBAAoB,CAAC;AAAA,EACnC;AAGA,SAAO,KAAK;AAAA,EAAK,MAAM,iBAAiB,CAAC,EAAE;AAE3C,SAAO;AACT;",
   "names": ["getEnvInfoPrompt"]
 }