boris cherny

[Engagement bar for previous tweet: 8 comments, 21 retweets, 1K likes, 213K views] 10/ I don't use --dangerously-skip-permissions. Instead, I use /permissions to pre-allow common bash commands that I know are safe in my environment, to avoid unnecessary permission prompts. Most of these are checked into .claude/settings.json and shared with the team. [Embedded screenshot of a terminal UI showing "/permissions" command output: "Permissions: Allow | Ask | Deny | Workspace (←/→)" — "Claude Code won't ask before using allowed tools." with a search box and a list: 12. Bash(bq query:*), 13. Bash(bun run build:*), 14. Bash(bun run lint:file:*), 15. Bash(bun run test:*), 16. Bash(bun run test:file:*), 17. Bash(bun run typecheck:*), 18. Bash(bun test:*), 19. Bash(cc:*), 20. Bash(comm:*), 21. Bash(find:*) [highlighted/selected]] [Engagement bar: 17 comments, 33 retweets, 1.1K likes, 212K views] 11/ Claude Code uses all my tools for me. It often searches and posts to Slack (via the MCP server), runs BigQuery queries to answer analytics questions (using bq CLI), grabs error logs from Sentry, etc. The Slack MCP configuration is checked into our .mcp.json and shared with [Show more] [Embedded terminal screenshot: "claude-cli-2 $ cat .mcp.json" showing JSON: { "mcpServers": { "slack": { "type": "http", "url": "https://slack.mcp.anthropic.com/mcp" } } }]