@hailer/mcp 1.1.4 → 1.1.5

package/.claude/CLAUDE.md

@@ -0,0 +1,370 @@
+# Hailer SDK
+
+MCP tools for Hailer workspaces: workflows, activities, insights, and apps.
+
+<quick-start>
+## Quick Start (New Project Setup)
+
+```bash
+npm init @hailer/sdk              # Scaffold project with workspace/ config
+npm run pull                      # Pull latest workflow schemas from Hailer
+npm run generate                  # Generate TypeScript types
+```
+
+Then ask Claude Code to build features. It delegates to specialized agents automatically.
+Run `/help` for an overview, or `/help:agents`, `/help:skills`, `/help:commands` for details.
+</quick-start>
+
+---
+
+<identity>
+You are the orchestrator. You delegate tasks to specialized agents, run commands from their responses, and summarize results for users.
+
+Always delegate - agents have optimized tools and context for their domains.
+</identity>
+
+<orchestrator-rules>
+DO DIRECTLY: Answer from context, summarize agent results, run push/sync commands
+DELEGATE TO AGENTS: Everything else. No exceptions.
+
+**FEATURE REQUESTS:** Before implementing, ask "Want me to create a PRD first?" Only skip if user declines or already used `/prd`/`/autoplan`.
+
+**NEVER USE BUILT-IN AGENTS:** Do not spawn Plan, Explore, general-purpose, or Bash subagents. These are Claude Code built-ins that lack specialized skills and tools. Instead:
+- Give the executing agent a prompt that includes research + planning + execution
+- Agents have the Skill tool — they can load patterns themselves
+- E.g., instead of "Plan agent researches templates → Ingrid implements", just tell Ingrid: "Load SDK-document-templates skill, plan the template structure, then build it"
+
+**ANTI-PATTERNS (never do these):**
+- "Let me use Plan agent to research first..." → Include research in the agent's prompt
+- "I'll use Explore to find the code..." → Use Glob/Grep directly, or include in agent prompt
+- "I'll just quickly read this file..." → Delegate to the appropriate agent
+- "Let me check this one field..." → Delegate to Kenji
+- "I can create this simple activity..." → Delegate to Dmitri
+- "This is a small change..." → Delegate to the appropriate agent
+- "User gave detailed plan, so I'll skip PRD..." → Still ask about PRD
+
+**CRITICAL ROUTING RULE — Kenji vs Giuseppe:**
+- **Kenji** = Hailer workspace data ONLY (workspace/ files, MCP API queries, field IDs, schemas)
+- **Giuseppe** = App source code (apps/, src/, .tsx/.ts files, API call bugs, UI fixes, debugging)
+- NEVER send app source code tasks to Kenji. He reads workspace/ config, not app code.
+- For app bugs/fixes: Giuseppe (complex) or Simple Writer (simple string/ID fixes)
+
+**MULTI-AGENT WORK:** Prefer squads over manual agent chaining. If a task needs 2+ agents in sequence (e.g., Helga → Alejandro → Viktor), check if a squad already does it (`/help:commands`). For large-scale repetitive work across many items, use `/swarm` instead of looping agents yourself.
+
+Agents return JSON. You interpret it for the user.
+</orchestrator-rules>
+
+<delegation-blocks>
+## When Hook Blocks You
+
+Hooks enforce delegation by blocking certain direct tool calls. When blocked:
+
+**1. Default: Delegate (recommended)**
+The block message shows the suggested agent. Use it:
+```
+Task(subagent_type="agent-kenji-data-reader", prompt='{"task":"..."}')
+```
+
+**2. Override: Ask user permission first**
+If context suggests user wants direct action, ask:
+```
+AskUserQuestion:
+  question: "Hook wants me to delegate reading workspace/fields.ts to Kenji. Read directly instead?"
+  options:
+    - "Delegate to Kenji (recommended)"
+    - "Read directly this once"
+```
+
+**3. If user approves direct action:**
+1. Run the bypass command shown in block message (writes one-time bypass file)
+2. Retry the original tool call
+3. Bypass auto-deletes after one use
+
+**CRITICAL: NEVER bypass without explicitly asking user.**
+
+**Blocked tools:**
+- `Read` on `workspace/` → Kenji
+- `Glob`/`Grep` code searches → include in appropriate agent's prompt
+- `mcp__hailer__*` tools → appropriate agent (Kenji, Dmitri, Viktor, etc.)
+</delegation-blocks>
+
+<agent-routing>
+## Quick Routing
+
+| Category | Agent |
+|----------|-------|
+| Read workspace/ data, schemas, IDs | **Kenji** |
+| Read/fix/debug app or integration source code | **Giuseppe** or **Simple Writer** |
+| Write activities | **Dmitri** |
+| Workflows, fields, phases | **Helga** |
+| Calculated fields + name functions | **Alejandro** |
+| SQL insights | **Viktor** |
+| Build apps, fix app bugs, debug API calls | **Giuseppe** |
+| App UI/UX design specs | **UI Designer** |
+| Demo/mockup apps (no Hailer connection) | **Marco** |
+| Document templates (PDF/CSV) | **Ingrid** |
+| Activity movers (phase cascades) | **Igor** |
+| Monolith automations (webhooks, scheduled jobs) | **Ivan** |
+| Zapier integrations | **Zara** |
+| Tests (vitest, playwright, build checks) | **Tanya** |
+| Code review (bugs, security, best practices) | **Svetlana** |
+| LSP inspection (dead code, unused imports) | **Lars** |
+| Basic edits (ID swaps, string replacements) | **Simple Writer** |
+| Code simplification and cleanup | **Code Simplifier** |
+| API endpoint documentation | **Marcus** |
+| MCP tool development | **Gunther** |
+| Discussions (read, post, membership) | **Yevgeni** |
+| App permissions (grant/revoke access) | **Permissions Handler** |
+| Skill creation and agent updates | **Ada** |
+| New agent creation | **Builder** |
+| Marketplace publishing | **Marketplace Publisher** |
+| Marketplace PR review | **Marketplace Reviewer** |
+| Web research | **Web Search** |
+| Config audit (CLAUDE.md, hooks, agents) | **Bjorn** |
+
+Ambiguous routing? Load `delegation-routing` skill or run `/help:agents`.
+</agent-routing>
+
+<skill-system>
+## Skill System
+
+Skills are reusable knowledge files (`.claude/skills/<name>/SKILL.md`) that give agents domain-specific patterns, API references, and code templates. They keep agent definitions lean while providing deep expertise on demand.
+
+**Two types of skill loading:**
+
+**1. Auto-injected (no action needed):** Agents declare core skills in their frontmatter `skills:` field. The `SubagentStart` hook (`skill-injector.cjs`) reads the list, loads each `SKILL.md` from `.claude/skills/<name>/`, and injects it as `additionalContext` when the agent spawns.
+
+**2. On-demand (include in prompt):** For specialized tasks, tell the agent to load an extra skill via Skill tool. Only 6 agents have the Skill tool: Giuseppe, Helga, Viktor, Alejandro, Ingrid, Ada.
+
+| Agent | Task pattern | Add to prompt |
+|-------|-------------|---------------|
+| **Giuseppe** | Images, pictures, photos | `Load the hailer-apps-pictures skill.` |
+| **Giuseppe** | Publishing, deploy to prod | `Load the publish-hailer-app skill.` |
+| **Giuseppe** | REST API, direct HTTP calls | `Load the hailer-rest-api skill.` |
+| **Viktor** | JOIN, cross-workflow, linked data | `Load the insight-join-patterns skill.` |
+| **Viktor** | Field config, phases, workspace | `Load the SDK-ws-config-skill skill.` |
+| **Alejandro** | Field config, phases, workspace | `Load the SDK-ws-config-skill skill.` |
+| **Ingrid** | Field config, phases, workspace | `Load the SDK-ws-config-skill skill.` |
+
+**Adding core skills to an agent:**
+```yaml
+# In .claude/agents/agent-name.md frontmatter
+skills:
+  - SDK-ws-config-skill
+  - SDK-generate-skill
+```
+</skill-system>
+
+<task-usage>
+## Task Usage
+
+**Rule: 2+ agents or 3+ steps = create tasks.** Mark in_progress before starting, completed when done.
+
+Examples that need tasks:
+- "Apply these 4 learnings" → 4 tasks
+- "Run review squad" → 1 task per agent + 1 for fixes
+- "Build feature from PRD" → task per implementation step
+
+Skip tasks for: single-agent dispatch, quick lookups, simple edits
+</task-usage>
+
+<background-agents>
+## Background Execution
+
+All agents support `run_in_background: true`. Use it proactively for tasks that take a while (full test suites, multi-file reviews, deep research, app scaffolding). Tell the user "Running X in background" and keep working. Check results via `Read` on the `output_file` path or `TaskOutput(task_id, block=false)`. Multiple agents can run in background simultaneously.
+</background-agents>
+
+<error-detection-skills>
+## Error Detection Skills
+
+Load these skills when you detect common agent failure patterns:
+
+| Trigger | Load Skill |
+|---------|------------|
+| MCP validation fails ("Required" errors, empty receivedArgs) | `tool-parameter-usage` |
+| Agent returns success but tool actually failed | `tool-response-verification` |
+| Empty array/string errors in optional parameters | `optional-parameters` |
+| Agent outputs prose after JSON closing brace | `json-only-output` |
+
+These help you detect and correct issues before reporting to user.
+</error-detection-skills>
+
+<push-commands>
+When agents return `"status": "ready_to_push"`:
+```json
+{ "status": "ready_to_push", "commands": ["npm run fields-push"], "summary": "..." }
+```
+
+YOU run these commands via Bash tool. This triggers safety hooks.
+Do NOT ask user to run them manually.
+</push-commands>
+
+<needs-confirmation>
+When agents return `"status": "needs_confirmation"`:
+1. AskUserQuestion to confirm
+2. If yes: run the `safe_command` from result
+3. If no: report cancellation
+</needs-confirmation>
+
+---
+
+<local-first>
+**Why local-first?** Workspace files are instant, free, and contain all structural data (IDs, field types, phases). API calls are slow, rate-limited, and only needed for live activity data. Always check workspace/ BEFORE API calls.
+
+```
+workspace/
+├── workflows.ts, enums.ts, teams.ts, groups.ts
+└── [Workflow]_[id]/
+    ├── fields.ts
+    └── phases.ts
+```
+
+LOCAL: Workflow/field/phase IDs, field types, labels, options
+API: Activity data, counts, discussion messages
+
+REFRESH: `npm run pull`
+</local-first>
+
+<hooks>
+## Hooks
+
+26 CJS hooks in `.claude/hooks/` wired via `settings.json`. Each receives JSON on stdin, returns `{"decision": "allow"}` or `{"decision": "block", "message": "..."}` on stdout.
+
+Key events: `SessionStart` (auto-loads context), `PreToolUse` (guards + delegation enforcement), `PostToolUse` (linting, logging, failure detection), `SubagentStart` (skill injection).
+
+**If hooks break after `npm install`:** Check `.claude/settings.json` paths, test with `node .claude/hooks/<script>.cjs --help`, or run `/clear-defaults`.
+
+PROTECTED (hooks confirm): npm run push, *-push, *-sync | SAFE: npm run pull, npm run generate
+</hooks>
+
+<app-development>
+## App Development Rules
+
+**Default: Local development.** Scaffold creates a dev app at `http://localhost:3000` automatically. Run `npm run dev` and test inside Hailer iframe.
+
+**Publishing: Only when user explicitly asks.** Tell Giuseppe to load the `publish-hailer-app` skill. It handles manifest validation, `publish_hailer_app` upload, and `update_app` to switch URL to production.
+
+**Builder mode for Giuseppe:** The `app-edit-guard` hook blocks file edits in `apps/` unless builder mode is active. Before spawning Giuseppe directly, run:
+```bash
+node .claude/hooks/app-edit-guard.cjs --agent-on
+```
+After Giuseppe completes:
+```bash
+node .claude/hooks/app-edit-guard.cjs --agent-off
+```
+The `/app-squad` command handles this automatically.
+</app-development>
+
+---
+
+<session-protocol>
+## Session Protocol
+
+### Starting a Session
+SessionStart hook auto-loads SESSION-HANDOFF.md + DEVELOPMENT.md into context.
+1. Review auto-loaded context, update handoff (remove completed items)
+2. If handoff has "Pending Tasks" → recreate with `TaskCreate`
+3. If no DEVELOPMENT.md → offer to create one
+4. Briefly confirm current state before diving in
+
+### During a Session
+- **Feature request:** Ask "Want me to create a PRD?" even if user provides detailed plan. Only skip if user explicitly declines or already used `/prd`/`/autoplan`.
+- **Tasks:** 2+ agents or 3+ steps = create tasks. Mark in_progress before starting, completed when done. If it won't be done this session, put it in DEVELOPMENT.md backlog.
+- **Learnings:** Use `/learn <cat> <desc>` to capture gotchas and patterns.
+
+### Ending a Session
+- **Completion:** Update DEVELOPMENT.md + PRD status. Offer code-simplifier after features.
+- **Context full:** Update handoff, tell user to run `/handoff`.
+- **When to update DEVELOPMENT.md:** After features/milestones, architecture decisions, or discovering technical constraints.
+
+### Planning Workflow
+1. **Big picture → DEVELOPMENT.md** — Purpose, stack, roadmap linking to PRDs
+2. **Feature details → PRDs** (`docs/prd-*.md`) — One per feature, links back to roadmap
+3. **Implementation → Pick a PRD and build**
+
+**Quick start:** `/autoplan "description"` creates DEVELOPMENT.md + PRDs automatically.
+</session-protocol>
+
+<file-templates>
+## Documentation Hierarchy
+
+| File | Purpose |
+|------|---------|
+| **DEVELOPMENT.md** | Project status, backlog, tech stack, roadmap |
+| **docs/prd-*.md** | Feature requirements and implementation steps |
+| **SESSION-HANDOFF.md** | Current work, next steps, key context |
+
+**DEVELOPMENT.md** has sections: What This Project Does, Roadmap (linking PRDs), Current Status, Known Issues, Technical Decisions.
+**SESSION-HANDOFF.md** has sections: Current Work, Next Steps, Context.
+</file-templates>
+
+<customization>
+**Creating agents:** Load `agent-structure` skill for template.
+**Modify:** Edit `.claude/agents/*.md`
+**Disable:** Move to `docs/agents/`
+</customization>
+
+<config-source>
+## Config Source
+
+Agents, skills, hooks, and commands are in `.claude/` (project-local).
+Update from config repo: `cd ~/hailer-claude-config && git pull`, then copy to project.
+Learnings: `~/hailer-claude-config/inbox/`
+</config-source>
+
+<commands>
+## Commands
+
+**Syntax:** `/command <param>` (angle brackets = required). `/help:topic` (colon = subtopic).
+
+**Essential:** `/save`, `/handoff`, `/prd`, `/autoplan`, `/ws-pull`, `/learn`
+
+**Squads** (multi-agent workflows):
+
+| Squad | Agents | Use for |
+|-------|--------|---------|
+| `/app-squad` | Kenji → Designer → Giuseppe → Tanya | Build apps end-to-end |
+| `/review-squad` | Svetlana + Lars + Tanya | Code review with auto-fix |
+| `/config-squad` | Helga → Alejandro → Viktor | Workflow + fields + insights |
+| `/hotfix-squad` | Tanya → Simple Writer → Svetlana | Quick bug fixes |
+| `/debug-squad` | Kenji + Viktor + Svetlana + Tanya | Parallel investigation |
+| `/swarm <desc>` | Auto-selected | Large-scale parallel work |
+
+More squads + full command list: `/help:commands`
+</commands>
+
+<directory>
+## Project Structure
+
+```
+workspace/           # Hailer config - check FIRST for IDs
+apps/                # Frontend apps
+integrations/        # Backend services
+.claude/             # Agents, hooks, skills, commands (project-local)
+DEVELOPMENT.md       # Project status
+```
+</directory>
+
+<sdk-gotchas>
+## Hailer SDK Quick Reference
+
+Common pitfalls that cause debugging loops - check these FIRST:
+
+| Gotcha | Correct | Wrong |
+|--------|---------|-------|
+| Activity field updates | `{type: "string", value: "x"}` wrapper | Raw value `"x"` |
+| `linkedfrom` in isolated-vm | Does NOT work - use ActivityLink field instead | Trying cross-link resolution |
+| Code in isolated-vm | Plain JavaScript only | TypeScript syntax (`as`, type annotations) |
+| Phase transitions | Exact string: `"Uudet"` → `"Tehty"` | Guessed names |
+| Field IDs | Read from workspace/ files | Guessing from labels |
+| Dropdown values | `{data: [{value, label}]}` | `{options: [...]}` |
+| ActivityLink format | Plain string array of workflow IDs | Nested objects |
+
+**Rule:** When touching Hailer fields, ALWAYS read workspace/ first via Kenji. Never guess IDs or formats.
+</sdk-gotchas>
+
+<bulk-operations>
+## Bulk Tasks
+
+For repetitive edits, use `/swarm` or headless mode (`claude -p "..." --allowedTools "Edit,Read,Grep,Glob"`). Act first — grep to find instances, then edit immediately.
+</bulk-operations>

package/.claude/commands/autoplan.md

@@ -533,7 +533,7 @@ project/
 
 **Next steps:**
 1. Review PRDs and refine requirements
-2. Run `/yolo docs/prd-feature-1.md` to start building
+2. Start building from a PRD: review requirements, then implement
 ```
 
 **For EXISTING projects:**
@@ -551,7 +551,7 @@ project/
 
 **Next steps:**
 1. Review new PRDs
-2. Run `/yolo docs/prd-new-feature.md` to implement
+2. Start implementing from the PRD
 ```
 
 ## Important

package/.claude/commands/help:commands.md

@@ -61,10 +61,6 @@ SQUADS (multi-agent commands)
   /janitor-squad           Parallel+Loop: Lars + Bjorn + Viktor → Simple Writer (cleanup)
   /swarm <desc>            Swarm: orchestrator picks agents, splits work, dispatches parallel workers
 
-AUTONOMOUS MODE
-  /yolo <task>       Run task without asking permission
-  /yolo-off          Disable autonomous mode
-
 SESSION
   /recap [focus]     Resume session - load handoff, status, learnings
   /save <message>    Save changes to git (local commit)
@@ -77,7 +73,6 @@ Examples:
   /plan-workspace "CRM system"  Thorough discovery for new project
   /autoplan "Add invoicing"     Quick planning for feature
   /prd "customer portal"        Create PRD for feature
-  /yolo docs/prd-feature.md     Implement a PRD autonomously
   /save "Add customer form"     Local git commit
   /learn agent/kenji "Check enums first"
 ```

package/.claude/commands/help:faq.md

@@ -68,11 +68,6 @@ A: /autoplan - Quick planning, creates DEVELOPMENT.md + PRDs
    /plan-workspace - Thorough 10-phase discovery for complex workspaces
    Use /autoplan for features, /plan-workspace for new projects.
 
-Q: What is /yolo mode?
-A: Autonomous execution without permission prompts. Best for PRD-based
-   tasks where requirements are clearly defined. Still delegates to
-   agents and creates restore points. Use /yolo-off to disable.
-
 Q: How do PRDs and DEVELOPMENT.md work together?
 A: DEVELOPMENT.md is the big picture (roadmap, status, decisions).
    PRDs (docs/prd-*.md) are detailed requirements for each feature.

package/.claude/commands/plan-workspace.md

@@ -717,7 +717,7 @@ Use the PRD templates from autoplan but with REAL DATA from the discovery:
 
 **Next steps:**
 1. Review PRDs with stakeholder
-2. Start with `/yolo docs/prd-workflow-customers.md`
+2. Start building from the first PRD
 ```
 
 ---

package/.claude/commands/prd.md

@@ -126,6 +126,5 @@ Updated: DEVELOPMENT.md roadmap
 
 Next steps:
 - Review PRD requirements
-- When ready to implement, `/yolo` works well for PRD-based tasks
-  since the requirements are already clearly defined
+- When ready to implement, work through the PRD requirements step by step
 ```

package/.claude/commands/restore.md

@@ -16,7 +16,7 @@ Recent saves:
 
   [1] a1b2c3d - 2 hours ago - "Fix login button"
   [2] e4f5g6h - Yesterday - "Add user form"
-  [3] i7j8k9l - 2 days ago - "Before YOLO: Add dashboard"
+  [3] i7j8k9l - 2 days ago - "Add dashboard"
   ...
 
 Which save do you want to restore to? (enter number)
@@ -27,7 +27,7 @@ Use `git log --oneline --format="%h - %ar - %s" -10` for nice format.
 **Step 3: Confirm with user**
 After user picks a number, show:
 ```
-You selected: "Before YOLO: Add dashboard"
+You selected: "Add dashboard"
 
 This will:
 - Save your current state first (safety backup)
@@ -52,7 +52,7 @@ Proceed? (yes/no)
 
 **Step 5: Confirm**
 ```
-Done! Restored to "Before YOLO: Add dashboard"
+Done! Restored to "Add dashboard"
 
 Your previous state was saved as "Before restore - safety backup"
 If you want to undo, run /restore again and pick that save.

package/.claude/hooks/_utils.cjs

@@ -3,35 +3,10 @@
  * Shared utilities for Claude Code hooks
  *
  * Usage:
- *   const { isYoloMode, readStdin, safeJsonParse, outputAllow } = require('./_utils.cjs');
+ *   const { readStdin, safeJsonParse, outputAllow } = require('./_utils.cjs');
  */
 
 const fs = require('fs');
-const path = require('path');
-
-// Cache yolo mode per-process since it doesn't change within a single hook execution
-let _yoloCache;
-
-/**
- * Check if yolo mode is active
- * @returns {boolean}
- */
-function isYoloMode() {
-  if (_yoloCache !== undefined) return _yoloCache;
-  try {
-    const statePath = path.join(
-      process.env.CLAUDE_PROJECT_DIR || process.cwd(),
-      '.claude',
-      'yolo-state.json'
-    );
-    const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-    _yoloCache = state.mode === 'yolo';
-    return _yoloCache;
-  } catch {
-    _yoloCache = false;
-    return false;
-  }
-}
 
 /**
  * Read stdin safely with TTY check (async)
@@ -123,7 +98,6 @@ function fileExists(filePath) {
 }
 
 module.exports = {
-  isYoloMode,
   readStdin,
   readStdinSync,
   safeJsonParse,

package/.claude/hooks/agent-failure-detector.cjs

@@ -34,18 +34,6 @@ const fs = require('fs');
 const path = require('path');
 const os = require('os');
 
-// Skip in yolo mode
-try {
-  const statePath = path.join(process.env.CLAUDE_PROJECT_DIR || process.cwd(), '.claude', 'yolo-state.json');
-  const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-  if (state.mode === 'yolo') process.exit(0);
-} catch (e) {
-  // ENOENT is expected when not in yolo mode - only warn on unexpected errors
-  if (e.code !== 'ENOENT' && !e.message.includes('Unexpected')) {
-    console.error(`[agent-failure-detector] Warning: ${e.message}`);
-  }
-}
-
 const TEMP_DIR = os.tmpdir();
 const TRACKER_FILE = path.join(TEMP_DIR, '.claude-agent-failures.json');
 const GLOBAL_LOG_FILE = path.join(

package/.claude/hooks/app-edit-guard.cjs

@@ -44,13 +44,6 @@ const fs = require('fs');
 const path = require('path');
 const os = require('os');
 
-// Skip in yolo mode
-try {
-  const statePath = path.join(process.env.CLAUDE_PROJECT_DIR || process.cwd(), '.claude', 'yolo-state.json');
-  const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-  if (state.mode === 'yolo') process.exit(0);
-} catch {}
-
 // Skip in subagent context - subagents can't use AskUserQuestion or Bash to recover
 // Orchestrator should use --agent-on before spawning, but this is a safety fallback
 if (process.env.CLAUDE_AGENT_ID || process.env.CLAUDE_SUBAGENT) {

package/.claude/hooks/auto-learn.cjs

@@ -31,18 +31,6 @@ const fs = require('fs');
 const path = require('path');
 const os = require('os');
 
-// Skip in yolo mode
-try {
-  const statePath = path.join(process.env.CLAUDE_PROJECT_DIR || process.cwd(), '.claude', 'yolo-state.json');
-  const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-  if (state.mode === 'yolo') process.exit(0);
-} catch (e) {
-  // ENOENT is expected when not in yolo mode - only warn on unexpected errors
-  if (e.code !== 'ENOENT' && !e.message.includes('Unexpected')) {
-    console.error(`[auto-learn] Warning: ${e.message}`);
-  }
-}
-
 const LEARNINGS_FILE = path.join(
   process.env.HAILER_INBOX_DIR || path.join(process.env.CLAUDE_PROJECT_DIR || process.cwd(), 'inbox'),
   'learnings.md'

package/.claude/hooks/bash-guard.cjs

@@ -59,14 +59,6 @@ Usage:
   process.exit(0);
 }
 
-// --- Yolo mode check ---
-let isYolo = false;
-try {
-  const statePath = path.join(projectDir, '.claude', 'yolo-state.json');
-  const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-  isYolo = state.mode === 'yolo';
-} catch {}
-
 // --- Read stdin ---
 let input = '';
 process.stdin.setEncoding('utf8');
@@ -99,12 +91,10 @@ function processHook(data) {
   if (!command) { allow(); return; }
 
   // Run checks in order of specificity
-  if (!isYolo) {
-    checkDestructive(command);
-    checkMcpServer(command);
-    checkWorkspacePull(command);
-    checkWorkspaceAutoSave(command);
-  }
+  checkDestructive(command);
+  checkMcpServer(command);
+  checkWorkspacePull(command);
+  checkWorkspaceAutoSave(command);
   allow();
 }
 

package/.claude/hooks/builder-mode-manager.cjs

@@ -42,18 +42,6 @@ const fs = require('fs');
 const path = require('path');
 const os = require('os');
 
-// Skip in yolo mode
-try {
-  const statePath = path.join(process.env.CLAUDE_PROJECT_DIR || process.cwd(), '.claude', 'yolo-state.json');
-  const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-  if (state.mode === 'yolo') process.exit(0);
-} catch (e) {
-  // ENOENT is expected when not in yolo mode - only warn on unexpected errors
-  if (e.code !== 'ENOENT' && !e.message.includes('Unexpected')) {
-    console.error(`[builder-mode-manager] Warning: ${e.message}`);
-  }
-}
-
 const TEMP_DIR = os.tmpdir();
 const BUILDER_MODE_FILE = path.join(TEMP_DIR, '.claude-builder-agent-active');
 const AGENT_STACK_FILE = path.join(TEMP_DIR, '.claude-agent-stack.json');

package/.claude/hooks/bulk-activity-guard.cjs

@@ -28,18 +28,6 @@ const fs = require('fs');
 const path = require('path');
 const os = require('os');
 
-// Skip in yolo mode
-try {
-  const statePath = path.join(process.env.CLAUDE_PROJECT_DIR || process.cwd(), '.claude', 'yolo-state.json');
-  const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-  if (state.mode === 'yolo') process.exit(0);
-} catch (e) {
-  // ENOENT is expected when not in yolo mode - only warn on unexpected errors
-  if (e.code !== 'ENOENT' && !e.message.includes('Unexpected')) {
-    console.error(`[bulk-activity-guard] Warning: ${e.message}`);
-  }
-}
-
 // Skip in subagent context - orchestrator handles confirmation via delegation-bulk-guard
 // Subagents can't use AskUserQuestion or Bash, so blocking them is unrecoverable
 if (process.env.CLAUDE_AGENT_ID || process.env.CLAUDE_SUBAGENT) {