@iaforged/context-code 1.0.77 → 1.0.79

package/context-bootstrap.js

@@ -1,27 +1,27 @@
-#!/usr/bin/env node
-import { existsSync } from 'fs'
-import { homedir } from 'os'
-import { dirname, join } from 'path'
-import { fileURLToPath, pathToFileURL } from 'url'
-
-const __dirname = dirname(fileURLToPath(import.meta.url))
-
-if (!process.env.CLAUDE_CONFIG_DIR) {
-  process.env.CLAUDE_CONFIG_DIR = join(homedir(), '.context')
-}
-
-const isBun = typeof Bun !== 'undefined'
-const bundledCli = join(__dirname, 'cli.js')
-const distCli = join(__dirname, 'dist', 'src', 'entrypoints', 'cli.js')
-
-// cli.js es un bundle de Bun — solo usarlo si realmente corremos en Bun
-if (isBun && existsSync(bundledCli)) {
-  await import(pathToFileURL(bundledCli).href)
-} else if (existsSync(distCli)) {
-  await import(pathToFileURL(distCli).href)
-} else {
-  throw new Error(
-    'Context Code: no se encontró ningún punto de entrada.\n' +
-    'Reinstala el paquete: npm i -g @iaforged/context-code'
-  )
-}
+#!/usr/bin/env node
+import { existsSync } from 'fs'
+import { homedir } from 'os'
+import { dirname, join } from 'path'
+import { fileURLToPath, pathToFileURL } from 'url'
+
+const __dirname = dirname(fileURLToPath(import.meta.url))
+
+if (!process.env.CLAUDE_CONFIG_DIR) {
+  process.env.CLAUDE_CONFIG_DIR = join(homedir(), '.context')
+}
+
+const isBun = typeof Bun !== 'undefined'
+const bundledCli = join(__dirname, 'cli.js')
+const distCli = join(__dirname, 'dist', 'src', 'entrypoints', 'cli.js')
+
+// cli.js es un bundle de Bun — solo usarlo si realmente corremos en Bun
+if (isBun && existsSync(bundledCli)) {
+  await import(pathToFileURL(bundledCli).href)
+} else if (existsSync(distCli)) {
+  await import(pathToFileURL(distCli).href)
+} else {
+  throw new Error(
+    'Context Code: no se encontró ningún punto de entrada.\n' +
+    'Reinstala el paquete: npm i -g @iaforged/context-code'
+  )
+}

package/dist/src/bootstrap/state.js

@@ -580,6 +580,9 @@ export function getModelStrings() {
 export function setModelStrings(modelStrings) {
     STATE.modelStrings = modelStrings;
 }
+export function clearModelStrings() {
+    STATE.modelStrings = null;
+}
 // Test utility function to reset model strings for re-initialization.
 // Separate from setModelStrings because we only want to accept 'null' in tests.
 export function resetModelStringsForTestingOnly() {

package/dist/src/bridge/bridgeMain.js

@@ -1410,56 +1410,56 @@ async function printHelp() {
     const modes = EXTERNAL_PERMISSION_MODES.join(', ');
     const showServer = await isMultiSessionSpawnEnabled();
     const serverOptions = showServer
-        ? `  --spawn <mode>                   Spawn mode: same-dir, worktree, session
-                                   (default: same-dir)
-  --capacity <N>                   Max concurrent sessions in worktree or
-                                   same-dir mode (default: ${SPAWN_SESSIONS_DEFAULT})
-  --[no-]create-session-in-dir     Pre-create a session in the current
-                                   directory; in worktree mode this session
-                                   stays in cwd while on-demand sessions get
-                                   isolated worktrees (default: on)
+        ? `  --spawn <mode>                   Spawn mode: same-dir, worktree, session
+                                   (default: same-dir)
+  --capacity <N>                   Max concurrent sessions in worktree or
+                                   same-dir mode (default: ${SPAWN_SESSIONS_DEFAULT})
+  --[no-]create-session-in-dir     Pre-create a session in the current
+                                   directory; in worktree mode this session
+                                   stays in cwd while on-demand sessions get
+                                   isolated worktrees (default: on)
 `
         : '';
     const serverDescription = showServer
-        ? `
-  Remote Control runs as a persistent server that accepts multiple concurrent
-  sessions in the current directory. One session is pre-created on start so
-  you have somewhere to type immediately. Use --spawn=worktree to isolate
-  each on-demand session in its own git worktree, or --spawn=session for
-  the classic single-session mode (exits when that session ends). Press 'w'
-  during runtime to toggle between same-dir and worktree.
+        ? `
+  Remote Control runs as a persistent server that accepts multiple concurrent
+  sessions in the current directory. One session is pre-created on start so
+  you have somewhere to type immediately. Use --spawn=worktree to isolate
+  each on-demand session in its own git worktree, or --spawn=session for
+  the classic single-session mode (exits when that session ends). Press 'w'
+  during runtime to toggle between same-dir and worktree.
 `
         : '';
     const serverNote = showServer
-        ? `  - Worktree mode requires a git repository or WorktreeCreate/WorktreeRemove hooks
+        ? `  - Worktree mode requires a git repository or WorktreeCreate/WorktreeRemove hooks
 `
         : '';
-    const help = `
-Remote Control - Connect your local environment to claude.ai/code
-
-USAGE
-  claude remote-control [options]
-OPTIONS
-  --name <name>                    Name for the session (shown in claude.ai/code)
+    const help = `
+Remote Control - Connect your local environment to claude.ai/code
+
+USAGE
+  claude remote-control [options]
+OPTIONS
+  --name <name>                    Name for the session (shown in claude.ai/code)
 ${feature('KAIROS')
-        ? `  -c, --continue                   Resume the last session in this directory
-  --session-id <id>                Resume a specific session by ID (cannot be
-                                   used with spawn flags or --continue)
+        ? `  -c, --continue                   Resume the last session in this directory
+  --session-id <id>                Resume a specific session by ID (cannot be
+                                   used with spawn flags or --continue)
 `
-        : ''}  --permission-mode <mode>         Permission mode for spawned sessions
-                                   (${modes})
-  --debug-file <path>              Write debug logs to file
-  -v, --verbose                    Enable verbose output
-  -h, --help                       Show this help
-${serverOptions}
-DESCRIPTION
-  Remote Control allows you to control sessions on your local device from
-  claude.ai/code (https://claude.ai/code). Run this command in the
-  directory you want to work in, then connect from the Claude app or web.
-${serverDescription}
-NOTES
-  - You must be logged in with a Claude account that has a subscription
-  - Run \`claude\` first in the directory to accept the workspace trust dialog
+        : ''}  --permission-mode <mode>         Permission mode for spawned sessions
+                                   (${modes})
+  --debug-file <path>              Write debug logs to file
+  -v, --verbose                    Enable verbose output
+  -h, --help                       Show this help
+${serverOptions}
+DESCRIPTION
+  Remote Control allows you to control sessions on your local device from
+  claude.ai/code (https://claude.ai/code). Run this command in the
+  directory you want to work in, then connect from the Claude app or web.
+${serverDescription}
+NOTES
+  - You must be logged in with a Claude account that has a subscription
+  - Run \`claude\` first in the directory to accept the workspace trust dialog
 ${serverNote}`;
     // biome-ignore lint/suspicious/noConsole: intentional help output
     console.log(help);

package/dist/src/cli/print.js

@@ -152,18 +152,18 @@ const extractMemoriesModule = feature('EXTRACT_MEMORIES')
     ? require('../services/extractMemories/extractMemories.js')
     : null;
 /* eslint-enable @typescript-eslint/no-require-imports */
-const SHUTDOWN_TEAM_PROMPT = `<system-reminder>
-You are running in non-interactive mode and cannot return a response to the user until your team is shut down.
-
-You MUST shut down your team before preparing your final response:
-1. Use requestShutdown to ask each team member to shut down gracefully
-2. Wait for shutdown approvals
-3. Use the cleanup operation to clean up the team
-4. Only then provide your final response to the user
-
-The user cannot receive your response until the team is completely shut down.
-</system-reminder>
-
+const SHUTDOWN_TEAM_PROMPT = `<system-reminder>
+You are running in non-interactive mode and cannot return a response to the user until your team is shut down.
+
+You MUST shut down your team before preparing your final response:
+1. Use requestShutdown to ask each team member to shut down gracefully
+2. Wait for shutdown approvals
+3. Use the cleanup operation to clean up the team
+4. Only then provide your final response to the user
+
+The user cannot receive your response until the team is completely shut down.
+</system-reminder>
+
 Shut down your team and prepare your final response for the user.`;
 // Track message UUIDs received during the current session runtime
 const MAX_RECEIVED_UUIDS = 10_000;

package/dist/src/commands/agent/agent.js

@@ -14,6 +14,14 @@ function normalizeProviderInput(rawProvider) {
         case 'ollama_cloud':
         case 'ollamacloud':
             return 'ollama-cloud';
+        case 'gemini':
+        case 'gemini-api-key':
+        case 'google-ai':
+            return 'gemini-api';
+        case 'gemini-google':
+        case 'google':
+        case 'google-oauth':
+            return 'gemini-google';
         default:
             return rawProvider.trim().toLowerCase();
     }

package/dist/src/commands/commit-push-pr.js

@@ -26,14 +26,14 @@ function getPromptContent(defaultBranch, prAttribution) {
     let prefix = '';
     let reviewerArg = ' and `--reviewer anthropics/claude-code`';
     let addReviewerArg = ' (and add `--add-reviewer anthropics/claude-code`)';
-    let changelogSection = `
-
-## Changelog
-<!-- CHANGELOG:START -->
-[If this PR contains user-facing changes, add a changelog entry here. Otherwise, remove this section.]
+    let changelogSection = `
+
+## Changelog
+<!-- CHANGELOG:START -->
+[If this PR contains user-facing changes, add a changelog entry here. Otherwise, remove this section.]
 <!-- CHANGELOG:END -->`;
-    let slackStep = `
-
+    let slackStep = `
+
 5. After creating/updating the PR, check if the user's CLAUDE.md mentions posting to Slack channels. If it does, use ToolSearch to search for "slack send message" tools. If ToolSearch finds a Slack tool, ask the user if they'd like you to post the PR URL to the relevant Slack channel. Only post if the user confirms. If ToolSearch returns no results or errors, skip this step silently—do not mention the failure, do not attempt workarounds, and do not try alternative approaches.`;
     if (process.env.USER_TYPE === 'ant' && isUndercover()) {
         prefix = getUndercoverInstructions() + '\n';
@@ -42,54 +42,54 @@ function getPromptContent(defaultBranch, prAttribution) {
         changelogSection = '';
         slackStep = '';
     }
-    return `${prefix}## Context
-
-- \`SAFEUSER\`: ${safeUser}
-- \`whoami\`: ${username}
-- \`git status\`: !\`git status\`
-- \`git diff HEAD\`: !\`git diff HEAD\`
-- \`git branch --show-current\`: !\`git branch --show-current\`
-- \`git diff ${defaultBranch}...HEAD\`: !\`git diff ${defaultBranch}...HEAD\`
-- \`gh pr view --json number 2>/dev/null || true\`: !\`gh pr view --json number 2>/dev/null || true\`
-
-## Git Safety Protocol
-
-- NEVER update the git config
-- NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
-- 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
-- Do not commit files that likely contain secrets (.env, credentials.json, etc)
-- Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported
-
-## Your task
-
-Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request from the git diff ${defaultBranch}...HEAD output above).
-
-Based on the above changes:
-1. Create a new branch if on ${defaultBranch} (use SAFEUSER from context above for the branch name prefix, falling back to whoami if SAFEUSER is empty, e.g., \`username/feature-name\`)
-2. Create a single commit with an appropriate message using heredoc syntax${commitAttribution ? `, ending with the attribution text shown in the example below` : ''}:
-\`\`\`
-git commit -m "$(cat <<'EOF'
-Commit message here.${commitAttribution ? `\n\n${commitAttribution}` : ''}
-EOF
-)"
-\`\`\`
-3. Push the branch to origin
-4. If a PR already exists for this branch (check the gh pr view output above), update the PR title and body using \`gh pr edit\` to reflect the current diff${addReviewerArg}. Otherwise, create a pull request using \`gh pr create\` with heredoc syntax for the body${reviewerArg}.
-   - IMPORTANT: Keep PR titles short (under 70 characters). Use the body for details.
-\`\`\`
-gh pr create --title "Short, descriptive title" --body "$(cat <<'EOF'
-## Summary
-<1-3 bullet points>
-
-## Test plan
-[Bulleted markdown checklist of TODOs for testing the pull request...]${changelogSection}${effectivePrAttribution ? `\n\n${effectivePrAttribution}` : ''}
-EOF
-)"
-\`\`\`
-
-You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message.${slackStep}
-
+    return `${prefix}## Context
+
+- \`SAFEUSER\`: ${safeUser}
+- \`whoami\`: ${username}
+- \`git status\`: !\`git status\`
+- \`git diff HEAD\`: !\`git diff HEAD\`
+- \`git branch --show-current\`: !\`git branch --show-current\`
+- \`git diff ${defaultBranch}...HEAD\`: !\`git diff ${defaultBranch}...HEAD\`
+- \`gh pr view --json number 2>/dev/null || true\`: !\`gh pr view --json number 2>/dev/null || true\`
+
+## Git Safety Protocol
+
+- NEVER update the git config
+- NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
+- 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
+- Do not commit files that likely contain secrets (.env, credentials.json, etc)
+- Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported
+
+## Your task
+
+Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request from the git diff ${defaultBranch}...HEAD output above).
+
+Based on the above changes:
+1. Create a new branch if on ${defaultBranch} (use SAFEUSER from context above for the branch name prefix, falling back to whoami if SAFEUSER is empty, e.g., \`username/feature-name\`)
+2. Create a single commit with an appropriate message using heredoc syntax${commitAttribution ? `, ending with the attribution text shown in the example below` : ''}:
+\`\`\`
+git commit -m "$(cat <<'EOF'
+Commit message here.${commitAttribution ? `\n\n${commitAttribution}` : ''}
+EOF
+)"
+\`\`\`
+3. Push the branch to origin
+4. If a PR already exists for this branch (check the gh pr view output above), update the PR title and body using \`gh pr edit\` to reflect the current diff${addReviewerArg}. Otherwise, create a pull request using \`gh pr create\` with heredoc syntax for the body${reviewerArg}.
+   - IMPORTANT: Keep PR titles short (under 70 characters). Use the body for details.
+\`\`\`
+gh pr create --title "Short, descriptive title" --body "$(cat <<'EOF'
+## Summary
+<1-3 bullet points>
+
+## Test plan
+[Bulleted markdown checklist of TODOs for testing the pull request...]${changelogSection}${effectivePrAttribution ? `\n\n${effectivePrAttribution}` : ''}
+EOF
+)"
+\`\`\`
+
+You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message.${slackStep}
+
 Return the PR URL when you're done, so the user can see it.`;
 }
 const command = {

package/dist/src/commands/createMovedToPluginCommand.js

@@ -14,15 +14,15 @@ export function createMovedToPluginCommand({ name, description, progressMessage,
                 return [
                     {
                         type: 'text',
-                        text: `This command has been moved to a plugin. Tell the user:
-
-1. To install the plugin, run:
-   claude plugin install ${pluginName}@claude-code-marketplace
-
-2. After installation, use /${pluginName}:${pluginCommand} to run this command
-
-3. For more information, see: https://github.com/anthropics/claude-code-marketplace/blob/main/${pluginName}/README.md
-
+                        text: `This command has been moved to a plugin. Tell the user:
+
+1. To install the plugin, run:
+   claude plugin install ${pluginName}@claude-code-marketplace
+
+2. After installation, use /${pluginName}:${pluginCommand} to run this command
+
+3. For more information, see: https://github.com/anthropics/claude-code-marketplace/blob/main/${pluginName}/README.md
+
 Do not attempt to run the command. Simply inform the user about the plugin installation.`,
                     },
                 ];