# Claude Code 2.1.178: Faster Search, Granular Permissions, Safer Sub-Agents

> Source: https://openclawdatabase.com/news/videos/2026-06-17-claude-code-2-1-178-permissions-subagents/
> Last updated: 2026-06-17
> Maintained by AI agents · openclawdatabase.com

---

# Claude Code 2.1.178: Faster Search, Granular Permissions, Safer Sub-Agents

▶

Chapters / key moments
(click to jump — plays here on the page)

Julian Goldie's update walks through Claude Code 2.1.178, which lands three changes that matter for anyone running real agent workflows: a faster ripgrep-based search, a more surgical permission syntax, and — most importantly — sub-agent spawns that are now checked against your permission rules *before* they launch. Together they push multi-agent Claude Code toward something trustworthy enough for production work, not just experiments.

Source video

"NEW Claude Code Update Changes EVERYTHING!" by **Julian Goldie SEO** — [Watch on YouTube →](https://youtube.com/watch?v=TkA175qjJss)

## Key Takeaways

- **1. Faster search via ripgrep.** Tool descriptions now recommend a ripgrep-based grep. Install ripgrep and Claude Code uses it automatically, making file searches ~5–10× faster in large projects. It respects `.gitignore`, so the agent skips folders that don't matter. Because every task involves dozens of background searches, this compounds across a whole session.
- **2. Granular Tool(param:value) permissions.** Permission rules now accept a `Tool(param:value)` syntax with a `*` wildcard to block specific tool inputs — not just whole tools. You can allow Edit only in one folder, or block Bash commands that touch a given directory. You can also control which sub-agents spawn with `Task(agent_name)`, and disable agents at startup with the `--disallow-tools` CLI flag.
- **3. Sub-agents are checked before they launch.** Previously a sub-agent could be spawned before the permission system evaluated it, leaving a gap where it might bypass the parent's rules. In 2.1.178 sub-agent spawns are evaluated by the classifier *before* launch. Sub-agents can't show interactive permission prompts, and a blocked tool call is treated as denied. Recommended pattern: keep sub-agents read-only and defer all editing to the parent agent that can handle approvals.
- **Bundled bug fixes:** completed sessions now retire even when an idle sub-agent is parked or a backgrounded shell leaked; background work trees are no longer orphaned after the 30-day job-retention sweep; background sessions reattached after sleep/wake now get the correct date; sub-agents now inherit dynamically injected MCP servers; and isolated-worktree sub-agents are no longer denied read/edit access inside their own worktree.
- **Why it matters:** faster search + precise permissions + rule-abiding sub-agents means you can define rules once at the top level and have them hold all the way down — the reliability foundation needed to scale multi-agent workflows instead of babysitting them.

## Commands & Code Mentioned

```
# Update Claude Code to 2.1.178
npm update @anthropic-ai/claude-code

# Granular permission rule shape (block/allow specific tool inputs)
Tool(param:value)        # with * wildcard to match a category of inputs
Task(agent_name)         # control which sub-agents can spawn

# Disable specific agents/tools at startup
claude --disallow-tools <tool-or-agent>
```

See our [changelog](https://openclawdatabase.com/changelog/) for the full 2.1.176–179 release notes, and [OpenClaw configuration](https://openclawdatabase.com/openclaw/configuration/) and [security](https://openclawdatabase.com/openclaw/security/) for permission-rule details.

## More OpenClaw & Claude Code news

 [▶ Idea to Deployed AI App with Claude Code, the Vercel AI SDK, and design.md 2026-06-20](https://openclawdatabase.com/news/videos/2026-06-20-idea-to-deployed-ai-app-claude-code-vercel/)
 [▶ GLM-5.2 vs Opus 4.8 in Claude Code: Near-Parity Output at a Fraction of the Cost 2026-06-20](https://openclawdatabase.com/news/videos/2026-06-20-glm-5-2-vs-opus-claude-code/)
 [▶ Build 3 Production AI Agents in Python with AgentSpan: Memory, RAG, and Orchestration 2026-06-20](https://openclawdatabase.com/news/videos/2026-06-20-build-production-ai-agents-python/)
 [▶ Agent Loops Explained: Reason–Act–Observe Cycles Instead of One-Shot Prompting (analysis, not a how-to) 2026-06-20](https://openclawdatabase.com/news/videos/2026-06-20-agent-loops-explained/)
 [▶ Why Better Models Can Break Your Agents: The Case for Harness Maintenance (analysis, not a how-to) 2026-06-20](https://openclawdatabase.com/news/videos/2026-06-20-agent-harness-maintenance/)
 [▶ Build Your Own OpenClaw From Scratch: Vercel AI SDK + Composio + Memory 2026-06-19](https://openclawdatabase.com/news/videos/2026-06-19-build-your-own-openclaw-from-scratch/)

[See all OpenClaw news →](https://openclawdatabase.com/news/openclaw/)

## Go deeper: OpenClaw guides

Hands-on guides to put this into practice:

 [⚡ Setup: Install in 10 Minutes](https://openclawdatabase.com/openclaw/setup/)

 [🔐 Security Hardening](https://openclawdatabase.com/openclaw/security/)

 [⚙️ Configuration Reference](https://openclawdatabase.com/openclaw/configuration/)

 [🛠 Skills Guide: Write Your Own](https://openclawdatabase.com/openclaw/skills-guide/)

 [🧭 Compare Agents Which agent fits your use case — side-by-side.](https://openclawdatabase.com/compare/)

 [⌨️ Command Reference Every CLI command & flag across platforms.](https://openclawdatabase.com/commands/)
