
40 Hidden Claude Features, Settings & Shortcuts That Most Users Don't Know
AI features
- Views
- 1.0M
- Likes
- 542
- Reposts
- 89
- Comments
- 53
- Bookmarks
- 1.6K
TL;DR
A deep dive into 40 advanced Claude features across Chat, Code, and Cowork interfaces, including custom styles, project knowledge, automated coding rules, and parallel sub-agent processing.
Reading the ENGLISH translation
I've spent hundreds of hours inside every Claude interface.
Save this :)
These are the features that nobody talks about but everyone should be using.
Claude has three interfaces - Chat, Cowork, and Code. Most people use one. Almost nobody has explored all three. And even within the one they use, most people have touched maybe 20% of the available functionality.
The result is millions of people paying for a tool and using a fraction of what it can do.
Here are 40 features, settings, and shortcuts buried across the Claude ecosystem that change how you work the moment you discover them.
Claude Chat - Hidden Power
01. Styles: Go to Settings → Styles. Claude has preset communication styles you can switch between: Concise, Explanatory, Formal, and more. You can also create custom styles. Build one that matches your voice and every conversation starts with the right tone automatically.
02. Projects: Most people miss this entirely. Projects let you create persistent workspaces with their own instructions and files. Every conversation inside a project automatically inherits the context. Instead of pasting your context file every time, create a project and set the context once.
03. Project Knowledge: Inside any project, upload reference documents. Claude reads them at the start of every conversation. Your brand guidelines. Your product docs. Your writing samples. Always loaded. Never forgotten.
04. Custom Instructions (System Prompt): In Project settings, you can write custom instructions that act as a system prompt for every conversation. "You are my content strategist. Always respond in my brand voice. Never use these words: [list]. Always format outputs as: [format]." This runs silently behind every message.
05. Artifacts: When Claude produces code, documents, or visual outputs, they render in a separate panel. You can iterate on artifacts independently of the conversation. Edit, refine, and download without losing your chat context.
06. Memory: Claude now remembers things across conversations. It learns your preferences, your projects, and your communication style over time. You can view and edit what Claude remembers in Settings → Memory. Curate it like you would curate an employee's onboarding notes.
07. Deep Research: Toggle on Deep Research for any query and Claude runs extended searches, reading dozens of sources before producing a comprehensive research report. Think of it as a junior analyst spending 2 hours on research, delivered in 2 minutes.
08. File Upload Intelligence: You can upload PDFs, images, spreadsheets, CSVs, code files, and documents directly into chat. Claude does not just store them - it reads and understands them. Upload a 50-page report and ask specific questions about page 37. Upload a spreadsheet and ask for trend analysis.
09. Image Analysis: Upload any image and Claude sees it with remarkable detail. Screenshots of errors, photos of whiteboards, charts, diagrams, handwritten notes, receipts, business cards. If it has visual information, Claude can extract and interpret it.
10. Canvas: Claude can generate visuals, diagrams, and interactive components directly in chat. Ask for a flowchart of your process. A comparison table. An organizational chart. A simple calculator. They render inline and are interactive.
11. LaTeX Rendering: For anyone working with math, statistics, or technical content, Claude renders LaTeX equations beautifully. Ask for formulas, derivations, or statistical outputs and they display properly formatted.
12. Conversation Branching: Edit any previous message and Claude regenerates the response from that point, creating a new branch. This lets you explore alternative approaches without losing your original conversation thread.
Claude Code - Power Features
13. The **CLAUDE.md** Hierarchy: Most users have one CLAUDE.md. Power users have three levels. User-level (~/.claude/CLAUDE.md) for personal preferences. Project-level (.claude/CLAUDE.md) for team standards. Directory-level for module-specific rules. They cascade and the most specific level wins.
14. Path-Specific Rules: Create files in .claude/rules/ with YAML frontmatter specifying glob patterns. A rule with paths: ["\\/\.test.\"] applies to every test file in your codebase automatically. Different standards for different file types without cluttering your main CLAUDE.md.
15. Plan Mode (Shift+Tab): Switch to plan mode before complex tasks. Claude creates a step-by-step plan, shows it for approval, and only executes after you agree. Essential for any task touching multiple files. The difference between clean execution and debugging chaos.
16. /compact: Compresses your conversation when context gets long. Claude keeps the important details but frees up context window space. Use this when Claude starts repeating mistakes or losing track of earlier decisions.
17. /memory: Shows exactly which memory files Claude Code has loaded for this session. If Claude is behaving inconsistently, run this to check whether the right context is actually active.
18. Custom Slash Commands: Build reusable commands in .claude/commands/ (personal) or ~/.claude/commands/ (global). A /review command that runs your code review checklist. A /test command that generates tests following your patterns. Ten minutes to create, hours saved over time.
19. Git Integration: Claude Code has native git awareness. It can commit, push, create branches, and even write commit messages based on the changes it made. "Commit everything with a descriptive message" actually works.
20. Multi-File Editing: Claude Code can read and edit multiple files in a single operation. Rename a function across your entire codebase. Update an import path in every file that references it. Refactor a component and update every file that uses it.
21. Test Generation: Point Claude Code at any function or module. "Write comprehensive tests for this." It generates test files that follow your project's testing conventions (if you set them in CLAUDE.md or path rules) including edge cases and error scenarios.
22. The -p Flag: Runs Claude Code in non-interactive, headless mode. Essential for CI/CD pipelines. Without it, your CI job hangs waiting for user input forever. With it, Claude runs autonomously and returns structured output.
23. --output-format json: Combined with --json-schema, Claude Code returns machine-parseable structured output. Your CI pipeline can automatically parse findings and post them as inline PR comments.
24. Independent Review Instances: The same Claude Code session that wrote code is biased toward its own decisions when reviewing. Always use a separate, fresh session for code review. The exam for Claude Certified Architect explicitly tests this concept.
Claude Cowork - Hidden Functionality
25. Sub-Agent Parallel Processing: When Cowork gets a large task, it can spin up multiple sub-agents that work simultaneously. Tell it to process 20 files and it divides them across 4-5 sub-agents running in parallel. What takes 30 minutes sequentially finishes in 6.
26. /schedule: Set recurring tasks. Daily briefings. Weekly cleanups. Monthly financial processing. Your computer needs to be on and Claude Desktop open, but the tasks run unattended. If your laptop sleeps during a run, it auto-runs when you reopen.
27. Connector Chaining: Combine multiple connectors in a single workflow. "Read my Gmail, check my calendar, pull relevant files from Drive, and create a meeting prep document." Four connectors, one instruction, zero tab switching.
28. Plugin Marketplace: Verified plugins at claude.com/plugins give you pre-built capabilities for specific roles. Product management. Marketing. Finance. Legal. Each plugin adds slash commands and skills tailored to that function.
29. Folder Instructions: Place a markdown file with instructions inside any folder. When Cowork works on files in that folder, it reads those instructions first. Different rules for different projects. Different formatting for different clients. Automatic context switching.
30. Sandbox Security: Everything Cowork does runs inside a sandboxed Linux VM. It cannot access files outside the folders you explicitly grant permission for. You control the blast radius. This is why Cowork is safe for production work.
31. Browser Bridge: When Claude in Chrome is installed alongside Cowork, the two work together. Cowork can delegate web research to Chrome, process the results locally, and continue the workflow. The best of both worlds.
32. Session History: Every Cowork session is logged with full details of what actions were taken, what files were modified, and what the output was. Review any past session to understand exactly what happened. Essential for debugging failed automations.
33. Token Usage Awareness: Cowork tasks consume 3-5x more tokens than regular chat. Batch related tasks into single sessions. Be specific to avoid back-and-forth clarification. Schedule heavy tasks for off-peak hours where throughput is reportedly higher.
34. Plugin Chaining: Combine multiple plugins in a single workflow. Your research plugin feeds into your analysis plugin feeds into your report plugin. Multi-step, multi-capability workflows triggered by one command.
Platform-Wide Settings
35. Usage Dashboard: Check your token consumption and usage patterns. If you are hitting limits, this shows you where your tokens are going so you can optimize.
36. Model Selection: Different tasks benefit from different models. Haiku is faster and cheaper for simple tasks. Sonnet balances speed and quality. Opus is the most capable for complex reasoning. Match the model to the task.
37. API Access: Your Claude subscription includes API credits. Build custom integrations, connect Claude to your own tools, or automate workflows that the standard interfaces do not support.
38. Team Sharing (Team/Enterprise plans): Share projects, skills, and configurations with your team. Everyone gets the same context, the same standards, and the same capabilities. Consistency across the entire organization.
39. Data Privacy Controls: You can opt out of your conversations being used for training. Check Settings → Privacy. For sensitive business work, verify your data handling preferences are set correctly.
40. Keyboard Shortcuts: Ctrl+/ shows all available shortcuts. Ctrl+Shift+O opens a new conversation. Ctrl+Shift+C copies the last response. These small efficiencies compound across hundreds of daily interactions.
TL;DR
40 features. All hidden in plain sight. 99% of users know maybe 10.
Claude is not one tool. It is three interfaces (Chat, Code, Cowork), each with layers of functionality most users never explore. The people who discover these features do not just save time - they operate on a completely different level.
Pick the 5 features most relevant to your work. Try them today. Each one unlocks a workflow you did not know was possible.
This list took hundreds of hours of exploration to compile. If it saved you time, you know what to do.
I post stuff like this regularly - AI tools, features, workflows, and things I actually use. No fluff.
Follow me @eng_khairallah1 for more automation architectures, workflow designs, and business AI playbooks.
hope this was useful for you, Khairallah ❤️


