[{"data":1,"prerenderedAt":47},["ShallowReactive",2],{"$f4EFV_7EP14_sCnThCuh7OWrGDq7poJQPHtNMn_eLHWE":3},{"date":4,"generated_at":5,"picks":6,"candidates_scanned":45,"candidates_scored":46},"2026-03-25","2026-03-25T05:30:00.000000+00:00",[7,21,34],{"rank":8,"title":9,"source":10,"url":11,"category":12,"tldr":13,"score":14,"scores":15,"why":20},1,"Auto mode for Claude Code","Claude Blog","https://claude.com/blog/auto-mode","Release","- Claude Code's biggest daily friction — approving every single file write and bash command — now has a middle path between babysitting and full danger mode\n- Auto mode uses a classifier that checks each tool call before it runs: safe actions proceed automatically, risky ones get blocked and Claude finds a different approach instead\n- You no longer need --dangerously-skip-permissions to get flow state — auto mode gives you speed without removing all guardrails\n- Currently research preview on Team plan. Enterprise and API access rolling out in the coming days\n- Anthropic recommends running it in isolated environments — the classifier reduces risk but doesn't eliminate it",86,{"direct_claude_relevance":16,"practical_utility":17,"novelty":18,"source_credibility":19},31,24,17,14,"Auto mode solves the exact tension every Claude Code user eventually hits: constant permission prompts kill flow, but --dangerously-skip-permissions is genuinely risky. The classifier-based middle ground is the right design — it lets Claude move fast on the 95% of safe actions while still catching potentially destructive ones. This is an official Anthropic release, posted by /u/ClaudeOfficial with Team plan access today, Enterprise and API following shortly.",{"rank":22,"title":23,"source":24,"url":25,"category":26,"tldr":27,"score":28,"scores":29,"why":33},2,"Claude Code with --dangerously-skip-permissions is a real attack surface. Lasso published research + an open-source defender worth knowing about.","Reddit r/ClaudeAI","https://www.reddit.com/r/ClaudeAI/comments/1s2qdh0/claude_code_with_dangerouslyskippermissions_is_a/","Guide","- When Claude reads files, fetches web pages, or gets output from MCP servers, it can't reliably tell your instructions apart from malicious ones hidden in that content\n- If you're running --dangerously-skip-permissions and Claude clones a repo with a poisoned README, it might just follow the embedded instructions with full system access\n- Attack vectors include hidden instructions in code comments, malicious web pages Claude fetches, edited Notion/GitHub/Slack pages through MCP connectors, and Base64/homoglyph-encoded payloads\n- Lasso Security released an open-source PostToolUse hook that scans tool outputs against 50+ detection patterns — warns rather than hard-blocks, takes ~5 minutes to set up",69,{"direct_claude_relevance":30,"practical_utility":31,"novelty":19,"source_credibility":32},25,22,8,"This is one of those posts worth bookmarking if you use --dangerously-skip-permissions regularly. The fundamental problem — Claude processes untrusted content with trusted privileges — isn't going away, and the attack vectors Lasso documented are concrete and reproducible. The open-source hook (github.com/lasso-security/claude-hooks) gives you a low-friction way to add a detection layer without rebuilding your workflow. Timing is great given yesterday's auto mode release — the two pieces complement each other.",{"rank":35,"title":36,"source":24,"url":37,"category":26,"tldr":38,"score":39,"scores":40,"why":44},3,"Agent Flow: A beautiful way to visualize what Claude Code does","https://www.reddit.com/r/ClaudeAI/comments/1s286nb/agent_flow_a_beautiful_way_to_visualize_what/","- Claude Code is a black box — you see what it built, not how it decided to build it. Agent Flow is a VS Code extension that makes the agent's decisions visible in real time\n- See live tool calls with timing and token costs, watch subagents spawn and coordinate, click into any step to inspect the full transcript\n- File attention heatmaps show which files Claude is reading and writing most — useful for catching unnecessary context reads that drain your usage budget",59,{"direct_claude_relevance":31,"practical_utility":41,"novelty":42,"source_credibility":43},18,12,7,"For anyone building agents on top of Claude or trying to debug why a Claude Code session consumed far more tokens than expected, visualizing the tool call chain is genuinely useful. The VS Code panel approach is the right UX — it runs alongside your editor without context switching. Open source at github.com/patoles/agent-flow with a demo video linked. Rough around the edges (VS Code only for now, iTerm2 coming) but the core loop of watch → debug → improve is immediately practical.",50,21,1776402243425]