bingocode 1.1.200-beta.9 → 1.1.201

package/src/commands/brain/brain.ts

@@ -19,7 +19,7 @@ export async function call(
     if (enable) {
       context.setAppState(prev => ({ ...prev, brainMode: true }))
       saveBrainMode(true)
-      onDone('✓ Brain Mode enabled — this session only.', { display: 'system' })
+      onDone('✓ Brain Mode enabled.', { display: 'system' })
     } else {
       context.setAppState(prev => ({ ...prev, brainMode: false }))
       saveBrainMode(false)

package/src/constants/prompts.ts

@@ -59,6 +59,7 @@ import { TICK_TAG } from './xml.js'
 import { logForDebugging } from '../utils/debug.js'
 import { loadMemoryPrompt } from '../memdir/memdir.js'
 import { isUndercover } from '../utils/undercover.js'
+import { getCurrentSessionBrainMode } from '../utils/sessionStorage.js'
 import { isMcpInstructionsDeltaEnabled } from '../utils/mcpInstructionsDelta.js'
 
 // Dead code elimination: conditional imports for feature-gated modules
@@ -927,30 +928,32 @@ The user context may include a \`terminalFocus\` field indicating whether the us
 }
 
 function getBrainPolicySection(): string | null {
-  const { getCurrentSessionBrainMode } = require('../utils/sessionStorage.js')
   if (!getInitialSettings().brainMode && !getCurrentSessionBrainMode()) return null
   return `# Brain Mode (/brain)
 
-You are the coordinator — the brain, not the hands. Your context window is precious
-strategic real estate. Implementation details are delegated noise; your job is
-thinking, deciding, and orchestrating.
+You are the high-dimensional thinker — the brain, not the hands. You and the user
+think at the same altitude, as peers reasoning about the system. Your context window
+is precious strategic real estate, reserved for understanding, deciding, and
+orchestrating.
 
-## Hard Constraints
+## Identity Mapping
 
-**You MUST NOT execute work directly.** Do NOT use Bash, Read, Grep, Glob, Write,
-Edit, or any other execution tool yourself. Your only tools are Agent (to delegate)
-and AskUserQuestion (to clarify). Everything else is forbidden.
+When the user says "do X", "check Y", "fix Z" — you hear "orchestrate X", "direct
+the investigation of Y", "have someone fix Z". Your doing IS orchestrating. This
+is not a restriction. It is the definition of your role.
 
-**Every task goes through sub-agents.** Even a single file read, even a one-line
-grep — delegate it. Your context must stay clean for strategic reasoning.
+## Constraints
 
-**When in doubt, spawn an agent.** If you're about to reach for a tool, stop.
-Write a prompt for an agent instead.
+Your only tools are Agent (to delegate) and AskUserQuestion (to clarify).
+
+Everything else goes through sub-agents. Your context stays clean for strategic reasoning.
+
+When in doubt, spawn an agent.
 
 ## Workflow
 
-1. **Analyze** — understand the user's request at the system level. What's the real
-   goal? What decisions need to be made?
+1. **Analyze** — understand the user's request at the system level. What is the
+   real goal? What decisions need to be made?
 2. **Decompose** — break into independent workstreams. Each workstream becomes an
    agent prompt with clear scope, context, and expected output.
 3. **Parallelize** — launch all independent agents simultaneously. Never serialize
@@ -961,9 +964,9 @@ Write a prompt for an agent instead.
 ## Agent Prompt Quality
 
 Each agent prompt must include:
-- What we're trying to accomplish and why
-- What's already known / ruled out
-- Specific files, line numbers, commands — never "investigate the bug"
+- What we are trying to accomplish and why
+- What is already known / ruled out
+- Specific files, line numbers — never "investigate the bug"
 - Expected output format (short report, code change, test results)
 - Whether to write code or only research
 
@@ -971,5 +974,14 @@ Each agent prompt must include:
 
 Report compressed: decisions made, blockers hit, next steps. Never narrate what
 agents are doing moment-by-moment. "Agent A found X, agent B confirmed Y. Decision:
-rollback needed." is enough.`
+rollback needed." is enough.
+
+## Sub-agent Capabilities
+
+Sub-agents have full access to: Bash (shell execution), Read (file reading),
+Write (file creation), Edit (precise string replacement), Grep (regex search),
+Glob (file pattern matching), WebFetch (URL content), WebSearch (web search),
+NotebookEdit (Jupyter editing), plus task management tools and any configured
+MCP servers.`
 }
+

package/src/hooks/useMergedTools.ts

@@ -22,12 +22,13 @@ export function useMergedTools(
   mcpTools: Tools,
   toolPermissionContext: ToolPermissionContext,
 ): Tools {
+  const brainMode = useAppState(s => s.brainMode ?? false)
   let replBridgeEnabled = false
   let replBridgeOutboundOnly = false
   return useMemo(() => {
     // assembleToolPool is the shared function that both REPL and runAgent use.
     // It handles: getTools() + MCP deny-rule filtering + dedup + MCP CLI exclusion.
-    const assembled = assembleToolPool(toolPermissionContext, mcpTools)
+    const assembled = assembleToolPool(toolPermissionContext, mcpTools, brainMode)
 
     return mergeAndFilterTools(
       initialTools,
@@ -38,6 +39,7 @@ export function useMergedTools(
     initialTools,
     mcpTools,
     toolPermissionContext,
+    brainMode,
     replBridgeEnabled,
     replBridgeOutboundOnly,
   ])