Claude's "Secret Codes": 8 Hidden Features Most Users Never Discover

Let's be upfront: there is no secret unlock code that turns Claude into a different, uncensored model, and any post claiming otherwise is selling clicks, not information. What actually exists is better than a rumor — a set of real, documented features tucked away in menus most people never open. Treat this as the "secret codes" list for getting more out of the tool you already have.

Code #1 — Projects with custom knowledge. Create a Project, attach reference documents, style guides, or past work, and add standing instructions once. Every chat inside that Project inherits the context automatically, so you stop pasting the same background paragraph into every new conversation.

Code #2 — Artifacts. When Claude generates code, a document, or a diagram, it can open in a separate panel instead of dumping raw text into the chat. You can keep iterating on the artifact directly, view a live preview for web code, and pull the final version out clean, without scrolling through revision history in the transcript.

Code #3 — Styles. Beyond the default tone, you can select or define a writing style — more formal, more concise, or a custom persona you describe once — and apply it consistently across chats instead of re-prompting "make this less robotic" every time.

Code #4 — Structured prompting with tags. Wrapping instructions in simple tags (like separating your task from your source material) noticeably improves how reliably Claude follows multi-part requests. It looks like a developer trick, but writers use it too for long, structured prompts with multiple constraints.

Code #5 — Claude Code. A terminal-based coding agent that can read your repository, make edits across multiple files, run commands, and explain what it changed — useful for teams who want an AI collaborator that lives in the command line instead of a browser tab.

Code #6 — Extended thinking. For harder reasoning tasks, Claude can spend more time working through a problem step by step before answering, instead of racing to the first plausible response. Save it for genuinely hard questions; it's slower by design.

Code #7 — Temporary chats and data controls. Not every conversation needs to be saved or used for training. Review your privacy settings for options to keep specific chats out of your history and out of model training, especially before pasting anything sensitive.

None of these require a special phrase or a workaround — just a few extra minutes in Settings and the Projects panel. That's usually how "secret" features work: they were documented the whole time, just never in the first screen you saw.