Happy New Year! In December, I shared 31 days of Claude Code...

In December, I shared 31 days of Claude Code features. Thanks for following along and the replies, the questions, the "wait it can do that?"
If you missed any (or want them all in one place), here it is.
Your 2026 terminal is about to be very different. 🧵

Don't waste tokens asking "can you run git status or tests?"
Just type: ! followed by your bash command
The ! prefix executes bash instantly and injects the output into context.
No model processing. No delay. No wasted tokens.

Want to try a “what if we…” approach?
Go wild → if it gets weird → Esc Esc to jump back to a clean checkpoint and revise.
You can rewind the conversion, code, or both.

Want Claude to actually think before answering when using the API?
Just add:
thinking: { type: "enabled", budget_tokens: 5000 }
Claude shows its step-by-step reasoning in thinking blocks before responding.

Accidentally closed your terminal? Laptop died? No problem.
claude --continue → picks up your last conversation instantly
claude --resume → shows a picker to choose any past session
Context preserved. Momentum restored.
Note: This was removed recently, you can just ask Claude now to remember details or update ClaudeMD file directly:

Want to save something to Claude's memory without opening a file?
Just start your message with #, for example:
# Always use bun instead of npm
Claude asks where to save it. Memory updated. Keep coding.

Tired of reaching for the mouse to edit your prompts?
Just type: /vim
Now you get full vim-style editing in Claude Code:
h j k l → navigate
ciw → change word
dd → delete line
w b → jump by word
Edit prompts at the speed of thought.

Want to use Claude Code in scripts, CI/CD, or automation?
Just add -p:
* claude -p "Fix the lint errors"
* claude -p "List all the functions " | grep "async"
* git diff | claude -p "Explain these changes"
AI in your pipeline.

Want to see what's eating your context window?
Type /context to see exactly what's consuming your token window including:
* The system prompt
* MCP servers
* Memory files
* and more
It's like having X-ray vision for your tokens.

& your prompt
↳ Sends the task to Claude Code on the web (runs in background)
claude --teleport session_abc123
↳ Pulls and resumes the session in your local terminal to continue working
Claude at home and on the go.

2023: "Check out my GitHub contribution graph"
2025: "Check out my Claude Code stats"
Just type /stats
Orange is the new green.

Claude Code now lets you name sessions.
/rename api-migration
→ Names your current session
/resume api-migration or claude --resume api-migration
→ Resumes the session
Your branches have names. Sessions should too.
Note: Typing Ultrathink still works, but the other thinking modes have been removed. See the thread for more info on how Claude Code thinking modes work now.

You can control how hard claude will think before giving you a response.
"think" → 4k thinking tokens
"think hard" → 10k thinking tokens
"ultrathink" → 31,999 thinking tokens
Just say the magic word anywhere in your prompt.

It's like git stash, but for your prompt.
Ctrl+S saves your draft. Send something else. Draft auto-restores.
No more copying to a scratchpad. No more losing your train of thought.

Claude Code has a customizable status bar.
/statusline puts info relevant to you at the bottom of Claude Code. Customize it however you want!
Git info, model, tokens, weather, Bitcoin price, prayer times, Wordle streak - it's your call.

Tired of Claude Code asking permission for everything?
claude --dangerously-skip-permissions
This flag says yes to everything. It has "danger" in the name, so please use it wisely.

Hooks are shell commands that run at predetermined lifecycle events.
Run /hooks or configure in .claude/settings.json.
Use hooks to block dangerous commands, provide notifications, and much more.
Deterministic control over probabilistic AI.

@ mentions in Claude Code may be overpowered:
* Add one or many files into context instantly
* Quickly list directories
* Enable/disable/invoke MCP servers and subagents
@ is the fastest path from "I need context" to "Claude has context."

Claude can predict what you'll ask next
Finish a task → see a grayed-out follow-up suggestion appear:
Tab → accept and edit
Enter → accept and run immediately
Tab used to autocomplete your code. Now it autocompletes your work.

Claude can now directly interact with your browser.
Navigating pages, clicking buttons, reading console errors, inspecting the DOM, and more.
"Fix the bug and verify it works" is now one prompt.
/chrome to start.

Skills = folders of instructions, scripts, and resources that teach Claude how to do specialized tasks.
Packaged once. Usable everywhere. And since Agent skills are now an open standard, I mean everywhere!

"Can you send me your Claude Code setup?"
sends 47 files across 12 directories
"...nevermind"
That era is over
/plugin install my-setup
Discover new workflows via marketplace
Commands, agents, skills, hooks, MCP. One package. One command.

Your past prompts are searchable within Claude Code.
Ctrl+R → reverse search through your prompt history
Ctrl+R again → cycle through matches
Enter → run it
Tab → edit first
Don't retype. Recall.

Everybody needs onboarding docs. With /init, Claude writes its own.
/init → Claude reads your codebase and generates a CLAUDEmd file with build commands, test instructions, key directories, conventions.
Claude onboards itself. Good Claude.

Sometimes you want receipts.
/export → dumps your entire conversation to markdown including every prompt, every response, every tool call.
For documentation. For training. For proving to your past self that yes, you did try that already.

Santa doesn't wrap every gift. He has elves.
Subagents are Claude's elves.
Each subagent gets it's own 200k context window, performs specialized tasks, runs in parallel and merges it's output back to main agent.
Delegate like Santa. 🎅

Save any prompt as a reusable command.
Single markdown file in. Slash command out. Accepts arguments too.
/explain $ARGUMENTS → /explain src/auth.ts
Stop repeating yourself.

"Can I run npm install?" [Allow]
"Can I run npm test?" [Allow]
"Can I cat this file?" [Allow]
×100
/sandbox → boundaries set → Claude gets to work.
Define boundaries once. Claude works freely inside them.
YOLO speed. Actual security.

"Am I about to hit my limit?"
/usage → check your limits
/extra-usage → remove your limits
Know your limits. Then exceed them.

Clear the fog of war first.
Shift+Tab twice → Plan mode.
Claude can read, search, analyze and explore your codebase but won't edit anything.
Think twice. Execute once.
Seriously though, I default to plan mode 90% of the time.

Language Server Protocol in Claude Code provides
- Instant diagnostics to see errors and warnings
- Navigation with go to definition, find references, and more
- Type info and docs for code symbols
Claude Code now has IDE-level code intelligence

I saved the best for last.
The same agent loop, tools, and context management that power Claude Code is available as an SDK.
Build agents that work like Claude Code in as little as 10 lines of code.
This is just the beginning. 🎇🥂
If 2025 was the year that AI really learned to code well, I predict 2026 will be the year we learn to better build with it.
Thank you again for tuning in and happy building!
