Claude for coding: what it is good at

Claude is good at reading and explaining code, writing and fixing functions, and working through larger changes step by step. Claude Code, Anthropic’s coding agent, goes further: it reads your whole codebase, edits files, runs commands and works with Git. Claude has a free plan; Claude Code needs a paid plan.

Claude in the chat app

In the regular Claude app you can paste code, describe a bug or ask for a script. Anthropic’s pricing page says the free plan can search the web, create files and run code, and create Artifacts, which are pieces of content such as a small web page or tool shown alongside the chat. That makes it handy for quick scripts, formulas and prototypes you can see straight away.

What Claude Code adds

Claude Code is an agentic coding tool. Instead of you copying code back and forth, it works directly on a project. According to Anthropic’s documentation it can:

• Read and explain an existing codebase.
• Plan an approach, then write code across multiple files.
• Run commands and tests, and trace bugs to their cause.
• Stage changes, write commit messages and open pull requests.
• Follow project instructions kept in a CLAUDE.md file.
• Connect to other tools through the Model Context Protocol (MCP).

It runs in the terminal, in VS Code and JetBrains editors, in a desktop app, on the web and in Slack. It is included in the Pro, Max, Team and Enterprise plans, not the free plan.

Where Kahu fitsKahu AssistKahu Assist is an AI agent that runs your website, marketing, bookings and follow-ups from one chat, and asks before anything goes live. You keep the yes; it does the typing.Connects to your site, WhatsApp, calendar and emailAsks before anything goes liveSet up from one 15-minute chatSee Kahu Assist →Fill Thursday’s empty slots and let the cafe know the new brunch hours.Kahu · 3 actions readyTwo Thursday gaps at 11:00 and 14:30. Drafted messages to 6 waitlisted customers.Updated the hours on your site and Google profile to Sat–Sun 8–2.One post about the new hours, using your Sunday counter photo.ChangeApprove all

Where it is strongest

Keep a person in charge

1. 1Start on a branchLet it work away from your live code, so nothing reaches customers by accident.
2. 2Write down the rulesPut your standards, preferred libraries and no-go areas in the project instructions file.
3. 3Review every diffRead what changed before you merge, the same as you would for a colleague.
4. 4Test it yourselfPassing tests are a good sign, not proof. Try the change as a user would.

Frequently asked questions