I've been using Claude Code pretty much every day for the last few months. It's become the tool I reach for first. Writing code, debugging, exploring unfamiliar codebases, documenting and even write blog posts 🙈.
But to be honest staring at editor panes can be a bit boring so what can we do to make Claude Code a bit more fun? What is there that isn't strictly about "writing code faster"? Here's a collecting of fun and interesting things you can do with Claude Code.
/insights - How are you actually using this thing?
Run /insights in Claude Code and it'll generate a report on how you've been using it. It breaks down your patterns. What kinds of tasks you're throwing at it, how often, what tools you're leaning on most. It's a bit like Spotify Wrapped but for your AI coding/vibing sessions.
Beyond the novelty factor, it's actually useful. It'll flag things like "you're spending a lot of time on X" or suggest ways to be more efficient. Like for me it suggested a few hooks I could add to speed up my workflow for mobile development. Sometimes you need a mirror held up to your ways of working.
/usage - Keep tabs on your allowance
This one's more practical than fun, but it's worth knowing about. /usage shows you exactly where you stand with your Claude Code allowance. Your current 6-hour window, weekly usage, how much headroom you've got left.
If you've ever hit the rate limit mid-flow and wanted to throw your laptop out the window, this command helps you plan around it. I tend to check it before starting something meaty. No point kicking off a big refactor if you're about to run dry.
It's become a bit of a boast across the Add Jam Slack to see who can max out their plan usage.
/color - Colour your sessions
Type /color followed by a colour name (red, blue, green, yellow, purple, orange, pink or cyan) and it changes the prompt bar colour for that session. It's purely cosmetic and completely pointless in the best way.
Where it actually becomes useful is when you're running multiple Claude Code sessions at once. Colour-code them by project or task and you can tell at a glance which terminal is which. Red for the API, blue for the frontend, green for tests. It's a small touch but it makes juggling sessions way easier.
ccusage - Third-party usage tracking
If you want even more detail on your usage patterns, ccusage is a community-built tool that tracks your Claude Code consumption over time. It gives you historical data, trends and helps you understand whether that "quick question" habit is actually eating through your allowance faster than you think.
Handy if you're on a team and want to get a sense of how much Claude Code is being used across the board.
PeonPing - "Your workers need attention"
This one is brilliant. If you've ever played Warcraft or Red Alert 2 on your biege box of a PC back in the day, you'll know the feeling of hearing "Job's done!" or "Kirov reporting" echoing from your speakers.
PeonPing brings that energy to Claude Code. It plays game character voice lines and shows visual overlay notifications when your AI coding agent needs your attention. Like when it's waiting for permission to run a command or it's finished a task and needs you to review something.
Instead of constantly tab-switching and cycling through panes to check if Claude's done, you get a Warcraft peon shouting "Work work" at you. It's completely ridiculous and I love it. There are voice packs from multiple games, TV shows and movies so you can pick your own nostalgia.
/btw - The shoulder tap
Mid-task and need to ask something unrelated? Type /btw followed by your question. Claude handles it without losing context on what you were working on.
It's like tapping a colleague on the shoulder to ask "what's the PostHog event name for signups again?" without derailing the conversation about the bug you're both debugging. Small feature, surprisingly useful.
Checkpointing - Time travel for your session
Press Esc twice and Claude Code lets you rewind to a previous checkpoint. It rolls back both the conversation and any code changes to that point.
Gone down a rabbit hole that turned out to be wrong? Don't start a new session. Just rewind to before the detour and try a different approach. It's saved me from the "I've been going in circles for 20 minutes" spiral more than once.
The vibes are real
The thing I like about all of this is that it shows Claude Code isn't just a utilitarian tool you grimly stare at all day. There's a community building fun things around it, the team shipping little quality-of-life touches and enough flexibility to make it feel like your tool rather than a generic one.
If you haven't poked around beyond the basics, spend ten minutes exploring. Type / and scroll through the commands. Check what the community is building. You'll probably find something that either saves you time or makes you smile. Ideally both.
If you're using AI tools to build software and want to chat about what's working (or not), drop us a line or book a quick call.
