@iaforged/context-code 1.2.12 → 1.3.6

package/dist/src/commands/terminalSetup/terminalSetup.js

@@ -136,8 +136,8 @@ export function markBackslashReturnUsed() {
 }
 export async function call(onDone, context, _args) {
     if (env.terminal && env.terminal in NATIVE_CSIU_TERMINALS) {
-        const message = `Shift+Enter is natively supported in ${NATIVE_CSIU_TERMINALS[env.terminal]}.
-
+        const message = `Shift+Enter is natively supported in ${NATIVE_CSIU_TERMINALS[env.terminal]}.
+
 No configuration needed. Just use Shift+Enter to add newlines.`;
         onDone(message);
         return null;
@@ -156,18 +156,18 @@ No configuration needed. Just use Shift+Enter to add newlines.`;
         }
         // For Linux and other platforms, we don't show native terminal options
         // since they're not currently supported
-        const message = `Terminal setup cannot be run from ${terminalName}.
-
-This command configures a convenient Shift+Enter shortcut for multi-line prompts.
-${chalk.dim('Note: You can already use backslash (\\\\) + return to add newlines.')}
-
-To set up the shortcut (optional):
-1. Exit tmux/screen temporarily
-2. Run /terminal-setup directly in one of these terminals:
-${platformTerminals}   • IDE: VSCode, Cursor, Windsurf, Zed
-   • Other: Alacritty
-3. Return to tmux/screen - settings will persist
-
+        const message = `Terminal setup cannot be run from ${terminalName}.
+
+This command configures a convenient Shift+Enter shortcut for multi-line prompts.
+${chalk.dim('Note: You can already use backslash (\\\\) + return to add newlines.')}
+
+To set up the shortcut (optional):
+1. Exit tmux/screen temporarily
+2. Run /terminal-setup directly in one of these terminals:
+${platformTerminals}   • IDE: VSCode, Cursor, Windsurf, Zed
+   • Other: Alacritty
+3. Return to tmux/screen - settings will persist
+
 ${chalk.dim('Note: iTerm2, WezTerm, Ghostty, Kitty, and Warp support Shift+Enter natively.')}`;
         onDone(message);
         return null;
@@ -180,13 +180,13 @@ async function installBindingsForVSCodeTerminal(editor = 'VSCode', theme) {
     // Check if we're running in a VSCode Remote SSH session
     // In this case, keybindings need to be installed on the LOCAL machine
     if (isVSCodeRemoteSSH()) {
-        return `${color('warning', theme)(`Cannot install keybindings from a remote ${editor} session.`)}${EOL}${EOL}${editor} keybindings must be installed on your local machine, not the remote server.${EOL}${EOL}To install the Shift+Enter keybinding:${EOL}1. Open ${editor} on your local machine (not connected to remote)${EOL}2. Open the Command Palette (Cmd/Ctrl+Shift+P) → "Preferences: Open Keyboard Shortcuts (JSON)"${EOL}3. Add this keybinding (the file must be a JSON array):${EOL}${EOL}${chalk.dim(`[
-  {
-    "key": "shift+enter",
-    "command": "workbench.action.terminal.sendSequence",
-    "args": { "text": "\\u001b\\r" },
-    "when": "terminalFocus"
-  }
+        return `${color('warning', theme)(`Cannot install keybindings from a remote ${editor} session.`)}${EOL}${EOL}${editor} keybindings must be installed on your local machine, not the remote server.${EOL}${EOL}To install the Shift+Enter keybinding:${EOL}1. Open ${editor} on your local machine (not connected to remote)${EOL}2. Open the Command Palette (Cmd/Ctrl+Shift+P) → "Preferences: Open Keyboard Shortcuts (JSON)"${EOL}3. Add this keybinding (the file must be a JSON array):${EOL}${EOL}${chalk.dim(`[
+  {
+    "key": "shift+enter",
+    "command": "workbench.action.terminal.sendSequence",
+    "args": { "text": "\\u001b\\r" },
+    "when": "terminalFocus"
+  }
 ]`)}${EOL}`;
     }
     const editorDir = editor === 'VSCode' ? 'Code' : editor;
@@ -336,9 +336,9 @@ async function enableOptionAsMetaForTerminal(theme) {
     }
 }
 async function installBindingsForAlacritty(theme) {
-    const ALACRITTY_KEYBINDING = `[[keyboard.bindings]]
-key = "Return"
-mods = "Shift"
+    const ALACRITTY_KEYBINDING = `[[keyboard.bindings]]
+key = "Return"
+mods = "Shift"
 chars = "\\u001B\\r"`;
     // Get Alacritty config file paths in order of preference
     const configPaths = [];

package/dist/src/commands.js

@@ -159,6 +159,7 @@ import swarmAuto from './commands/swarm-auto/index.js';
 import swarmInit from './commands/swarm-init/index.js';
 import team from './commands/team/index.js';
 import limites from './commands/limites/index.js';
+import objetivo from './commands/objetivo/index.js';
 import resumen from './commands/resumen/index.js';
 import outputStyle from './commands/output-style/index.js';
 import remoteEnv from './commands/remote-env/index.js';
@@ -238,6 +239,7 @@ const COMMANDS = memoize(() => [
     mcp,
     memory,
     mobile,
+    objetivo,
     agent,
     model,
     profile,

package/dist/src/components/PromptInput/PromptInput.js

@@ -1960,6 +1960,22 @@ function PromptInput({ debug, ideSelection, toolPermissionContext, setToolPermis
     }
     const textInputElement = isVimModeEnabled() ? _jsx(VimTextInput, { ...baseProps, initialMode: vimMode, onModeChange: setVimMode }) : _jsx(TextInput, { ...baseProps });
     return _jsxs(Box, { flexDirection: "column", marginTop: briefOwnsGap ? 0 : 1, children: [!isFullscreenEnvEnabled() && _jsx(PromptInputQueuedCommands, {}), hasSuppressedDialogs && _jsx(Box, { marginTop: 1, marginLeft: 2, children: _jsx(Text, { dimColor: true, children: "Waiting for permission\u2026" }) }), _jsx(PromptInputStashNotice, { hasStash: stashedPrompt !== undefined }), swarmBanner ? _jsxs(_Fragment, { children: [_jsx(Text, { color: swarmBanner.bgColor, children: swarmBanner.text ? _jsxs(_Fragment, { children: ['─'.repeat(Math.max(0, columns - stringWidth(swarmBanner.text) - 4)), _jsxs(Text, { backgroundColor: swarmBanner.bgColor, color: "inverseText", children: [' ', swarmBanner.text, ' '] }), '──'] }) : '─'.repeat(columns) }), _jsxs(Box, { flexDirection: "row", width: "100%", children: [_jsx(PromptInputModeIndicator, { mode: mode, isLoading: isLoading, viewingAgentName: viewingAgentName, viewingAgentColor: viewingAgentColor }), _jsx(Box, { flexGrow: 1, flexShrink: 1, onClick: handleInputClick, children: textInputElement })] }), _jsx(Text, { color: swarmBanner.bgColor, children: '─'.repeat(columns) })] }) : _jsxs(Box, { flexDirection: "row", alignItems: "flex-start", justifyContent: "flex-start", borderColor: getBorderColor(), borderStyle: "round", borderLeft: false, borderRight: false, borderBottom: true, width: "100%", borderText: buildBorderText(showFastIcon ?? false, showFastIconHint, fastModeCooldown), children: [_jsx(PromptInputModeIndicator, { mode: mode, isLoading: isLoading, viewingAgentName: viewingAgentName, viewingAgentColor: viewingAgentColor }), _jsx(Box, { flexGrow: 1, flexShrink: 1, onClick: handleInputClick, children: textInputElement })] }), _jsx(PromptInputFooter, { apiKeyStatus: apiKeyStatus, debug: debug, exitMessage: exitMessage, vimMode: isVimModeEnabled() ? vimMode : undefined, mode: mode, autoUpdaterResult: autoUpdaterResult, isAutoUpdating: isAutoUpdating, verbose: verbose, onAutoUpdaterResult: onAutoUpdaterResult, onChangeIsUpdating: setIsAutoUpdating, suggestions: suggestions, selectedSuggestion: selectedSuggestion, maxColumnWidth: maxColumnWidth, toolPermissionContext: effectiveToolPermissionContext, helpOpen: helpOpen, suppressHint: input.length > 0, isLoading: isLoading, tasksSelected: tasksSelected, teamsSelected: teamsSelected, bridgeSelected: bridgeSelected, tmuxSelected: tmuxSelected, teammateFooterIndex: teammateFooterIndex, ideSelection: ideSelection, mcpClients: mcpClients, isPasting: isPasting, isInputWrapped: isInputWrapped, messages: messages, isSearching: isSearchingHistory, historyQuery: historyQuery, setHistoryQuery: setHistoryQuery, historyFailedMatch: historyFailedMatch, onOpenTasksDialog: isFullscreenEnvEnabled() ? handleOpenTasksDialog : undefined }), isFullscreenEnvEnabled() ? null : autoModeOptInDialog, isFullscreenEnvEnabled() ?
+                // position=absolute takes zero layout height so the spinner
+                // doesn't shift when a notification appears/disappears. Yoga
+                // anchors absolute children at the parent's content-box origin;
+                // marginTop=-1 pulls it into the marginTop=1 gap row above the
+                // prompt border. In brief mode there is no such gap (briefOwnsGap
+                // strips our marginTop) and BriefSpinner sits flush against the
+                // border — marginTop=-2 skips over the spinner content into
+                // BriefSpinner's own marginTop=1 blank row. height=1 +
+                // overflow=hidden clips multi-line notifications to a single row.
+                // flex-end anchors the bottom line so the visible row is always
+                // the most recent. Suppressed while the slash overlay or
+                // auto-mode opt-in dialog is up by height=0 (NOT unmount) — this
+                // Box renders later in tree order so it would paint over their
+                // bottom row. Keeping Notifications mounted prevents AutoUpdater's
+                // initial-check effect from re-firing on every slash-completion
+                // toggle (PR#22413).
                 _jsx(Box, { position: "absolute", marginTop: briefOwnsGap ? -2 : -1, height: suggestions.length === 0 && !showAutoModeOptIn ? 1 : 0, width: "100%", paddingLeft: 2, paddingRight: 1, flexDirection: "column", justifyContent: "flex-end", overflow: "hidden", children: _jsx(Notifications, { apiKeyStatus: apiKeyStatus, autoUpdaterResult: autoUpdaterResult, debug: debug, isAutoUpdating: isAutoUpdating, verbose: verbose, messages: messages, onAutoUpdaterResult: onAutoUpdaterResult, onChangeIsUpdating: setIsAutoUpdating, ideSelection: ideSelection, mcpClients: mcpClients, isInputWrapped: isInputWrapped }) }) : null] });
 }
 /**

package/dist/src/components/PromptInput/PromptInputFooter.js

@@ -1,6 +1,6 @@
 import { MACRO, feature } from '../../recovery/bunBundleShim.js';
 import { jsx as _jsx, jsxs as _jsxs, Fragment as _Fragment } from "react/jsx-runtime";
-import { memo, useMemo, useRef } from 'react';
+import { memo, useEffect, useMemo, useRef, useState } from 'react';
 import { isBridgeEnabled } from '../../bridge/bridgeEnabled.js';
 import { getBridgeStatus } from '../../bridge/bridgeStatusUtil.js';
 import { useSetPromptOverlay } from '../../context/promptOverlayContext.js';
@@ -12,6 +12,7 @@ import { isFullscreenEnvEnabled } from '../../utils/fullscreen.js';
 import { isUndercover } from '../../utils/undercover.js';
 import { CoordinatorTaskPanel, useCoordinatorTaskCount } from '../CoordinatorAgentStatus.js';
 import { getLastAssistantMessageId, StatusLine, statusLineShouldDisplay } from '../StatusLine.js';
+import { formatearDuracion as formatearDuracionObjetivo } from '../../services/objetivo/types.js';
 import { Notifications } from './Notifications.js';
 import { PromptInputFooterLeftSide } from './PromptInputFooterLeftSide.js';
 import { PromptInputFooterSuggestions } from './PromptInputFooterSuggestions.js';
@@ -28,7 +29,21 @@ function PromptInputFooter({ apiKeyStatus, debug, exitMessage, vimMode, mode, au
     const coordinatorTaskCount = useCoordinatorTaskCount();
     const coordinatorTaskIndex = useAppState(s => s.coordinatorTaskIndex);
     const mainLoopModel = useAppState(s => s.mainLoopModelForSession ?? s.mainLoopModel);
-    const modelStatusText = isNarrow ? `Modelo: ${mainLoopModel}` : `ContextCode v${MACRO.VERSION} · Modelo activo: ${mainLoopModel}`;
+    const objetivo = useAppState(s => s.objetivo);
+    // Tick de 1s mientras hay objetivo activo para que el reloj del footer corra
+    // en tiempo real, no solo cuando cambia el AppState (que ocurre por turno).
+    const [, setObjetivoTick] = useState(0);
+    useEffect(() => {
+        if (!objetivo)
+            return;
+        const id = setInterval(() => setObjetivoTick(t => t + 1), 1000);
+        return () => clearInterval(id);
+    }, [objetivo]);
+    const objetivoIndicator = objetivo
+        ? `◎ objetivo · ${formatearDuracionObjetivo(Date.now() - objetivo.iniciadoEn)} · ${objetivo.turnos}t`
+        : '';
+    const baseStatusText = isNarrow ? `Modelo: ${mainLoopModel}` : `ContextCode v${MACRO.VERSION} · Modelo activo: ${mainLoopModel}`;
+    const modelStatusText = objetivoIndicator ? `${objetivoIndicator} · ${baseStatusText}` : baseStatusText;
     const pillSelected = tasksSelected && (coordinatorTaskCount === 0 || coordinatorTaskIndex < 0);
     const suppressHint = suppressHintFromProps || statusLineShouldDisplay(settings) || isSearching;
     const overlayData = useMemo(() => isFullscreen && suggestions.length ? { suggestions, selectedSuggestion, maxColumnWidth } : null, [isFullscreen, suggestions, selectedSuggestion, maxColumnWidth]);

package/dist/src/components/PromptInput/PromptInputQueuedCommands.js

@@ -31,9 +31,9 @@ const MAX_VISIBLE_NOTIFICATIONS = 3;
  * Create a synthetic overflow notification message for capped task notifications.
  */
 function createOverflowNotificationMessage(count) {
-    return `<${TASK_NOTIFICATION_TAG}>
-<${SUMMARY_TAG}>+${count} tareas más completadas</${SUMMARY_TAG}>
-<${STATUS_TAG}>completed</${STATUS_TAG}>
+    return `<${TASK_NOTIFICATION_TAG}>
+<${SUMMARY_TAG}>+${count} tareas más completadas</${SUMMARY_TAG}>
+<${STATUS_TAG}>completed</${STATUS_TAG}>
 </${TASK_NOTIFICATION_TAG}>`;
 }
 /**

package/dist/src/components/Spinner.js

@@ -227,6 +227,9 @@ function SpinnerWithVerbInner({ mode, loadingStartTimeRef, totalPausedMsRef, pau
         }
     }
     return _jsxs(Box, { flexDirection: "column", width: "100%", alignItems: "flex-start", children: [_jsx(SpinnerAnimationRow, { mode: mode, reducedMotion: reducedMotion, hasActiveTools: hasActiveTools, responseLengthRef: responseLengthRef, message: message, messageColor: messageColor, shimmerColor: shimmerColor, overrideColor: overrideColor, loadingStartTimeRef: loadingStartTimeRef, totalPausedMsRef: totalPausedMsRef, pauseStartTimeRef: pauseStartTimeRef, spinnerSuffix: spinnerSuffix, verbose: verbose, columns: columns, hasRunningTeammates: hasRunningTeammates, teammateTokens: teammateTokens, foregroundedTeammate: foregroundedTeammate, leaderIsIdle: leaderIsIdle, thinkingStatus: thinkingStatus, effortSuffix: effortSuffix }), showSpinnerTree && hasRunningTeammates ? _jsx(TeammateSpinnerTree, { selectedIndex: selectedIPAgentIndex, isInSelectionMode: viewSelectionMode === 'selecting-agent', allIdle: allIdle, leaderVerb: leaderIsIdle ? undefined : leaderVerb, leaderIdleText: leaderIsIdle ? 'Inactivo' : undefined, leaderTokenCount: leaderTokenCount }) : showExpandedTodos && tasksV2 && tasksV2.length > 0 ? _jsx(Box, { width: "100%", flexDirection: "column", children: _jsx(MessageResponse, { children: _jsx(TaskListV2, { tasks: tasksV2 }) }) }) : nextTask || effectiveTip || budgetText ?
+                // IMPORTANT: we need this width="100%" to avoid an Ink bug where the
+                // tip gets duplicated over and over while the spinner is running if
+                // the terminal is very small. TODO: fix this in Ink.
                 _jsxs(Box, { width: "100%", flexDirection: "column", children: [budgetText && _jsx(MessageResponse, { children: _jsx(Text, { dimColor: true, children: budgetText }) }), (nextTask || effectiveTip) && _jsx(MessageResponse, { children: _jsx(Text, { dimColor: true, children: nextTask ? `Siguiente: ${nextTask.subject}` : `Consejo: ${translateSpinnerTip(effectiveTip)}` }) })] }) : null] });
 }
 function BriefSpinner(t0) {

package/dist/src/components/agents/agentFileUtils.js

@@ -32,12 +32,12 @@ export function formatAgentAsMarkdown(agentType, whenToUse, tools, systemPrompt,
     const effortLine = effort !== undefined ? `\neffort: ${effort}` : '';
     const colorLine = color ? `\ncolor: ${color}` : '';
     const memoryLine = memory ? `\nmemory: ${memory}` : '';
-    return `---
-name: ${agentType}
-description: "${escapedWhenToUse}"${toolsLine}${modelLine}${providerLine}${effortLine}${colorLine}${memoryLine}
----
-
-${systemPrompt}
+    return `---
+name: ${agentType}
+description: "${escapedWhenToUse}"${toolsLine}${modelLine}${providerLine}${effortLine}${colorLine}${memoryLine}
+---
+
+${systemPrompt}
 `;
 }
 /**

package/dist/src/components/agents/generateAgent.js

@@ -8,105 +8,105 @@ import { isAutoMemoryEnabled } from '../../memdir/paths.js';
 import { logEvent, } from '../../services/analytics/index.js';
 import { jsonParse } from '../../utils/slowOperations.js';
 import { asSystemPrompt } from '../../utils/systemPromptType.js';
-const AGENT_CREATION_SYSTEM_PROMPT = `You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.
-
-**Important Context**: You may have access to project-specific instructions from CLAUDE.md files and other context that may include coding standards, project structure, and custom requirements. Consider this context when creating agents to ensure they align with the project's established patterns and practices.
-
-When a user describes what they want an agent to do, you will:
-
-1. **Extract Core Intent**: Identify the fundamental purpose, key responsibilities, and success criteria for the agent. Look for both explicit requirements and implicit needs. Consider any project-specific context from CLAUDE.md files. For agents that are meant to review code, you should assume that the user is asking to review recently written code and not the whole codebase, unless the user has explicitly instructed you otherwise.
-
-2. **Design Expert Persona**: Create a compelling expert identity that embodies deep domain knowledge relevant to the task. The persona should inspire confidence and guide the agent's decision-making approach.
-
-3. **Architect Comprehensive Instructions**: Develop a system prompt that:
-   - Establishes clear behavioral boundaries and operational parameters
-   - Provides specific methodologies and best practices for task execution
-   - Anticipates edge cases and provides guidance for handling them
-   - Incorporates any specific requirements or preferences mentioned by the user
-   - Defines output format expectations when relevant
-   - Aligns with project-specific coding standards and patterns from CLAUDE.md
-
-4. **Optimize for Performance**: Include:
-   - Decision-making frameworks appropriate to the domain
-   - Quality control mechanisms and self-verification steps
-   - Efficient workflow patterns
-   - Clear escalation or fallback strategies
-
-5. **Create Identifier**: Design a concise, descriptive identifier that:
-   - Uses lowercase letters, numbers, and hyphens only
-   - Is typically 2-4 words joined by hyphens
-   - Clearly indicates the agent's primary function
-   - Is memorable and easy to type
-   - Avoids generic terms like "helper" or "assistant"
-
-6 **Example agent descriptions**:
-  - in the 'whenToUse' field of the JSON object, you should include examples of when this agent should be used.
-  - examples should be of the form:
-    - <example>
-      Context: The user is creating a test-runner agent that should be called after a logical chunk of code is written.
-      user: "Please write a function that checks if a number is prime"
-      assistant: "Here is the relevant function: "
-      <function call omitted for brevity only for this example>
-      <commentary>
-      Since a significant piece of code was written, use the ${AGENT_TOOL_NAME} tool to launch the test-runner agent to run the tests.
-      </commentary>
-      assistant: "Now let me use the test-runner agent to run the tests"
-    </example>
-    - <example>
-      Context: User is creating an agent to respond to the word "hello" with a friendly jok.
-      user: "Hello"
-      assistant: "I'm going to use the ${AGENT_TOOL_NAME} tool to launch the greeting-responder agent to respond with a friendly joke"
-      <commentary>
-      Since the user is greeting, use the greeting-responder agent to respond with a friendly joke. 
-      </commentary>
-    </example>
-  - If the user mentioned or implied that the agent should be used proactively, you should include examples of this.
-- NOTE: Ensure that in the examples, you are making the assistant use the Agent tool and not simply respond directly to the task.
-
-Your output must be a valid JSON object with exactly these fields:
-{
-  "identifier": "A unique, descriptive identifier using lowercase letters, numbers, and hyphens (e.g., 'test-runner', 'api-docs-writer', 'code-formatter')",
-  "whenToUse": "A precise, actionable description starting with 'Use this agent when...' that clearly defines the triggering conditions and use cases. Ensure you include examples as described above.",
-  "systemPrompt": "The complete system prompt that will govern the agent's behavior, written in second person ('You are...', 'You will...') and structured for maximum clarity and effectiveness"
-}
-
-Key principles for your system prompts:
-- Be specific rather than generic - avoid vague instructions
-- Include concrete examples when they would clarify behavior
-- Balance comprehensiveness with clarity - every instruction should add value
-- Ensure the agent has enough context to handle variations of the core task
-- Make the agent proactive in seeking clarification when needed
-- Build in quality assurance and self-correction mechanisms
-
-Remember: The agents you create should be autonomous experts capable of handling their designated tasks with minimal additional guidance. Your system prompts are their complete operational manual.
+const AGENT_CREATION_SYSTEM_PROMPT = `You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.
+
+**Important Context**: You may have access to project-specific instructions from CLAUDE.md files and other context that may include coding standards, project structure, and custom requirements. Consider this context when creating agents to ensure they align with the project's established patterns and practices.
+
+When a user describes what they want an agent to do, you will:
+
+1. **Extract Core Intent**: Identify the fundamental purpose, key responsibilities, and success criteria for the agent. Look for both explicit requirements and implicit needs. Consider any project-specific context from CLAUDE.md files. For agents that are meant to review code, you should assume that the user is asking to review recently written code and not the whole codebase, unless the user has explicitly instructed you otherwise.
+
+2. **Design Expert Persona**: Create a compelling expert identity that embodies deep domain knowledge relevant to the task. The persona should inspire confidence and guide the agent's decision-making approach.
+
+3. **Architect Comprehensive Instructions**: Develop a system prompt that:
+   - Establishes clear behavioral boundaries and operational parameters
+   - Provides specific methodologies and best practices for task execution
+   - Anticipates edge cases and provides guidance for handling them
+   - Incorporates any specific requirements or preferences mentioned by the user
+   - Defines output format expectations when relevant
+   - Aligns with project-specific coding standards and patterns from CLAUDE.md
+
+4. **Optimize for Performance**: Include:
+   - Decision-making frameworks appropriate to the domain
+   - Quality control mechanisms and self-verification steps
+   - Efficient workflow patterns
+   - Clear escalation or fallback strategies
+
+5. **Create Identifier**: Design a concise, descriptive identifier that:
+   - Uses lowercase letters, numbers, and hyphens only
+   - Is typically 2-4 words joined by hyphens
+   - Clearly indicates the agent's primary function
+   - Is memorable and easy to type
+   - Avoids generic terms like "helper" or "assistant"
+
+6 **Example agent descriptions**:
+  - in the 'whenToUse' field of the JSON object, you should include examples of when this agent should be used.
+  - examples should be of the form:
+    - <example>
+      Context: The user is creating a test-runner agent that should be called after a logical chunk of code is written.
+      user: "Please write a function that checks if a number is prime"
+      assistant: "Here is the relevant function: "
+      <function call omitted for brevity only for this example>
+      <commentary>
+      Since a significant piece of code was written, use the ${AGENT_TOOL_NAME} tool to launch the test-runner agent to run the tests.
+      </commentary>
+      assistant: "Now let me use the test-runner agent to run the tests"
+    </example>
+    - <example>
+      Context: User is creating an agent to respond to the word "hello" with a friendly jok.
+      user: "Hello"
+      assistant: "I'm going to use the ${AGENT_TOOL_NAME} tool to launch the greeting-responder agent to respond with a friendly joke"
+      <commentary>
+      Since the user is greeting, use the greeting-responder agent to respond with a friendly joke. 
+      </commentary>
+    </example>
+  - If the user mentioned or implied that the agent should be used proactively, you should include examples of this.
+- NOTE: Ensure that in the examples, you are making the assistant use the Agent tool and not simply respond directly to the task.
+
+Your output must be a valid JSON object with exactly these fields:
+{
+  "identifier": "A unique, descriptive identifier using lowercase letters, numbers, and hyphens (e.g., 'test-runner', 'api-docs-writer', 'code-formatter')",
+  "whenToUse": "A precise, actionable description starting with 'Use this agent when...' that clearly defines the triggering conditions and use cases. Ensure you include examples as described above.",
+  "systemPrompt": "The complete system prompt that will govern the agent's behavior, written in second person ('You are...', 'You will...') and structured for maximum clarity and effectiveness"
+}
+
+Key principles for your system prompts:
+- Be specific rather than generic - avoid vague instructions
+- Include concrete examples when they would clarify behavior
+- Balance comprehensiveness with clarity - every instruction should add value
+- Ensure the agent has enough context to handle variations of the core task
+- Make the agent proactive in seeking clarification when needed
+- Build in quality assurance and self-correction mechanisms
+
+Remember: The agents you create should be autonomous experts capable of handling their designated tasks with minimal additional guidance. Your system prompts are their complete operational manual.
 `;
 // Agent memory instructions to include in the system prompt when memory is mentioned or relevant
-const AGENT_MEMORY_INSTRUCTIONS = `
-
-7. **Agent Memory Instructions**: If the user mentions "memory", "remember", "learn", "persist", or similar concepts, OR if the agent would benefit from building up knowledge across conversations (e.g., code reviewers learning patterns, architects learning codebase structure, etc.), include domain-specific memory update instructions in the systemPrompt.
-
-   Add a section like this to the systemPrompt, tailored to the agent's specific domain:
-
-   "**Update your agent memory** as you discover [domain-specific items]. This builds up institutional knowledge across conversations. Write concise notes about what you found and where.
-
-   Examples of what to record:
-   - [domain-specific item 1]
-   - [domain-specific item 2]
-   - [domain-specific item 3]"
-
-   Examples of domain-specific memory instructions:
-   - For a code-reviewer: "Update your agent memory as you discover code patterns, style conventions, common issues, and architectural decisions in this codebase."
-   - For a test-runner: "Update your agent memory as you discover test patterns, common failure modes, flaky tests, and testing best practices."
-   - For an architect: "Update your agent memory as you discover codepaths, library locations, key architectural decisions, and component relationships."
-   - For a documentation writer: "Update your agent memory as you discover documentation patterns, API structures, and terminology conventions."
-
-   The memory instructions should be specific to what the agent would naturally learn while performing its core tasks.
+const AGENT_MEMORY_INSTRUCTIONS = `
+
+7. **Agent Memory Instructions**: If the user mentions "memory", "remember", "learn", "persist", or similar concepts, OR if the agent would benefit from building up knowledge across conversations (e.g., code reviewers learning patterns, architects learning codebase structure, etc.), include domain-specific memory update instructions in the systemPrompt.
+
+   Add a section like this to the systemPrompt, tailored to the agent's specific domain:
+
+   "**Update your agent memory** as you discover [domain-specific items]. This builds up institutional knowledge across conversations. Write concise notes about what you found and where.
+
+   Examples of what to record:
+   - [domain-specific item 1]
+   - [domain-specific item 2]
+   - [domain-specific item 3]"
+
+   Examples of domain-specific memory instructions:
+   - For a code-reviewer: "Update your agent memory as you discover code patterns, style conventions, common issues, and architectural decisions in this codebase."
+   - For a test-runner: "Update your agent memory as you discover test patterns, common failure modes, flaky tests, and testing best practices."
+   - For an architect: "Update your agent memory as you discover codepaths, library locations, key architectural decisions, and component relationships."
+   - For a documentation writer: "Update your agent memory as you discover documentation patterns, API structures, and terminology conventions."
+
+   The memory instructions should be specific to what the agent would naturally learn while performing its core tasks.
 `;
 export async function generateAgent(userPrompt, model, existingIdentifiers, abortSignal) {
     const existingList = existingIdentifiers.length > 0
         ? `\n\nIMPORTANT: The following identifiers already exist and must NOT be used: ${existingIdentifiers.join(', ')}`
         : '';
-    const prompt = `Create an agent configuration based on this request: "${userPrompt}".${existingList}
+    const prompt = `Create an agent configuration based on this request: "${userPrompt}".${existingList}
   Return ONLY the JSON object, no other text.`;
     const userMessage = createUserMessage({ content: prompt });
     // Fetch user and system contexts

package/dist/src/components/design-system/FuzzyPicker.js

@@ -99,6 +99,9 @@ export function FuzzyPicker({ title, placeholder = 'Type to search…', initialQ
     // undefined (e.g. delete clears matches), switching row→fragment would
     // change both layout AND gap count, bouncing the searchBox below.
     const listGroup = renderPreview && previewPosition === 'right' ? _jsxs(Box, { flexDirection: "row", gap: 2, height: visibleCount + (matchLabel ? 1 : 0), children: [_jsxs(Box, { flexDirection: "column", flexShrink: 0, children: [listBlock, matchLabel && _jsx(Text, { dimColor: true, children: matchLabel })] }), preview ?? _jsx(Box, { flexGrow: 1 })] }) :
+        // Box (not fragment) so the outer gap={1} doesn't insert a blank line
+        // between list/matchLabel/preview — that read as extra space above the
+        // prompt in direction='up'.
         _jsxs(Box, { flexDirection: "column", children: [listBlock, matchLabel && _jsx(Text, { dimColor: true, children: matchLabel }), preview] });
     const inputAbove = direction !== 'up';
     return _jsx(Pane, { color: "permission", children: _jsxs(Box, { flexDirection: "column", gap: 1, tabIndex: 0, autoFocus: true, onKeyDown: handleKeyDown, children: [_jsx(Text, { bold: true, color: "permission", children: title }), inputAbove && searchBox, listGroup, !inputAbove && searchBox, _jsx(Text, { dimColor: true, children: _jsxs(Byline, { children: [_jsx(KeyboardShortcutHint, { shortcut: "\u2191/\u2193", action: compact ? 'nav' : 'navigate' }), _jsx(KeyboardShortcutHint, { shortcut: "Enter", action: compact ? firstWord(selectAction) : selectAction }), onTab && _jsx(KeyboardShortcutHint, { shortcut: "Tab", action: onTab.action }), onShiftTab && !compact && _jsx(KeyboardShortcutHint, { shortcut: "shift+tab", action: onShiftTab.action }), _jsx(KeyboardShortcutHint, { shortcut: "Esc", action: "cancelar" }), extraHints] }) })] }) });

package/dist/src/components/grove/Grove.js

@@ -8,16 +8,16 @@ import { Select } from '../CustomSelect/index.js';
 import { Byline } from '../design-system/Byline.js';
 import { Dialog } from '../design-system/Dialog.js';
 import { KeyboardShortcutHint } from '../design-system/KeyboardShortcutHint.js';
-const NEW_TERMS_ASCII = ` _____________
- |          \\  \\
- | NEW TERMS \\__\\
- |              |
- |  ----------  |
- |  ----------  |
- |  ----------  |
- |  ----------  |
- |  ----------  |
- |              |
+const NEW_TERMS_ASCII = ` _____________
+ |          \\  \\
+ | NEW TERMS \\__\\
+ |              |
+ |  ----------  |
+ |  ----------  |
+ |  ----------  |
+ |  ----------  |
+ |  ----------  |
+ |              |
  |______________|`;
 function GracePeriodContentBody() {
     const $ = _c(9);

package/dist/src/components/messages/CollapsedReadSearchContent.js

@@ -358,5 +358,8 @@ export function CollapsedReadSearchContent({ message, inProgressToolUseIDs, shou
                                 isActiveGroup,
                                 hasPrecedingParts: hasPrecedingNonMem || memParts.length > 0
                             }) : null, isActiveGroup && _jsx(Text, { children: "\u2026" }, "ellipsis"), " ", _jsx(CtrlOToExpand, {})] })] }), isActiveGroup && displayedHint !== undefined &&
+                // Row layout: 5-wide gutter for ⎿, then a flex column for the text.
+                // Ink's wrap stays inside the right column so continuation lines
+                // indent under ⎿. MAX_HINT_CHARS in commandAsHint caps total at ~5 lines.
                 _jsxs(Box, { flexDirection: "row", children: [_jsx(Box, { width: 5, flexShrink: 0, children: _jsx(Text, { dimColor: true, children: '  ⎿  ' }) }), _jsx(Box, { flexDirection: "column", flexGrow: 1, children: displayedHint.split('\n').map((line, i, arr) => _jsxs(Text, { dimColor: true, children: [line, i === arr.length - 1 && shellProgressSuffix] }, `hint-${i}`)) })] }), message.hookTotalMs !== undefined && message.hookTotalMs > 0 && _jsxs(Text, { dimColor: true, children: ['  ⎿  ', "Ran ", message.hookCount, " PreToolUse", ' ', message.hookCount === 1 ? 'hook' : 'hooks', " (", formatSecondsShort(message.hookTotalMs), ")"] })] });
 }

package/dist/src/components/permissions/AskUserQuestionPermissionRequest/AskUserQuestionPermissionRequest.js

@@ -290,11 +290,11 @@ function AskUserQuestionPermissionRequestBody(t0) {
                 }
                 return `- "${q_1.question}"\n  (No se proporcionó respuesta)`;
             }).join("\n");
-            const feedback = `El usuario desea aclarar estas preguntas.
-    Esto significa que pueden tener información adicional, contexto o preguntas para ti.
-    Ten en cuenta su respuesta y reformula las preguntas si es apropiado.
-    Comienza preguntándoles qué desearían aclarar.
-
+            const feedback = `El usuario desea aclarar estas preguntas.
+    Esto significa que pueden tener información adicional, contexto o preguntas para ti.
+    Ten en cuenta su respuesta y reformula las preguntas si es apropiado.
+    Comienza preguntándoles qué desearían aclarar.
+
     Preguntas realizadas:\n${questionsWithAnswers}`;
             if (metadataSource) {
                 logEvent("tengu_ask_user_question_respond_to_claude", {
@@ -331,9 +331,9 @@ function AskUserQuestionPermissionRequestBody(t0) {
                 }
                 return `- "${q_2.question}"\n  (No se proporcionó respuesta)`;
             }).join("\n");
-            const feedback_0 = `El usuario ha indicado que ha proporcionado suficientes respuestas para la entrevista del plan.
-Deja de hacer preguntas aclaratorias y procede a finalizar el plan con la información que tienes.
-
+            const feedback_0 = `El usuario ha indicado que ha proporcionado suficientes respuestas para la entrevista del plan.
+Deja de hacer preguntas aclaratorias y procede a finalizar el plan con la información que tienes.
+
 Preguntas realizadas y respuestas proporcionadas:\n${questionsWithAnswers_0}`;
             if (metadataSource) {
                 logEvent("tengu_ask_user_question_finish_plan_interview", {

package/dist/src/components/permissions/hooks.js

@@ -20,20 +20,20 @@ function permissionResultToLog(permissionResult) {
             const suggestions = rules.length > 0
                 ? rules.map(r => permissionRuleValueToString(r)).join(', ')
                 : 'none';
-            return `ask: ${permissionResult.message}, 
-suggestions: ${suggestions}
+            return `ask: ${permissionResult.message}, 
+suggestions: ${suggestions}
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         }
         case 'deny':
-            return `deny: ${permissionResult.message},
+            return `deny: ${permissionResult.message},
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         case 'passthrough': {
             const rules = extractRules(permissionResult.suggestions);
             const suggestions = rules.length > 0
                 ? rules.map(r => permissionRuleValueToString(r)).join(', ')
                 : 'none';
-            return `passthrough: ${permissionResult.message},
-suggestions: ${suggestions}
+            return `passthrough: ${permissionResult.message},
+suggestions: ${suggestions}
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         }
     }