# Meet your AI assistant that actually does things

**Author:** Ivan Misic  
**Published:** 2026-01-09  
**URL:** https://ivanmisic.net/blog/ai-tools/meet-your-ai-assistant

**TL;DR**

Claude Code can inspect a project, use the development tools available in its environment, and apply approved changes to real files. Its exact capability depends on the files, tools, and permissions you give the session. Your job is to decide the result, provide the constraints, review the technical approach and diff, run the checks that matter, and keep a recovery path. Start with a restorable project and one read-only request so you can check what it understood before allowing edits.

Claude Code is useful when you know what should exist but do not know how to build it.

You describe the result in plain English. It can inspect the project, read the relevant files, use installed tools, propose changes, and apply the changes you approve. You still decide what belongs there and whether the result is safe to keep.

I start with the terminal because it keeps the working folder, commands, and permissions in front of you. The same product is also available through desktop apps, supported editors, and a web interface. The interface changes, but your responsibility does not.

## What Claude Code actually does

A general AI conversation returns an answer. Claude Code can work inside an approved environment.

For a website project, that can mean reading the existing CSS, changing a template, running the test suite, and showing you the diff. For a folder of documents, it can mean finding a repeated name and preparing replacements. The exact capability depends on the files, tools, permissions, and environment available to the session.

Claude Code only works with the tools and permissions you give it. It is not a universal file editor that understands every format perfectly. A spreadsheet task may need a suitable library. A design file may need another tool. If the format is important, work on a copy and verify formulas, formatting, totals, and exports before replacing the original.

## What you remain responsible for

Claude Code can make a wrong change quickly. It can misunderstand the requirement, choose a weak technical approach, or edit more files than you expected.

Your job is to:

- decide what should happen
- give the relevant context and constraints
- review the proposed change
- run or inspect the checks that matter
- keep a recovery path

The knowledge is there. The judgment is yours.

More project context helps Claude make better choices, but it does not make verification optional. I give it project instructions, rules, and the files relevant to the task. I expand permissions only after I understand what the session needs to do.

## Terminal, desktop, or web

I would start in the terminal, as it makes every command and file change visible.

| Interface | Where the work runs | Good starting point for |
|---|---|---|
| Terminal | Your local or remote development environment | Learning the workflow and using existing command-line tools |
| Desktop app | Your computer for local sessions, or a cloud environment for remote sessions | Reviewing diffs and running several sessions without living in a terminal |
| Claude Code on the web | A cloud environment connected to a repository | Delegating repository tasks that can run away from your computer |
| Supported editor integration | Beside the code you are viewing | Moving between manual edits and Claude-assisted changes |
| Slack | A Claude Code web session connected to a repository | Starting repository tasks from a team conversation |
| Mobile | A cloud environment, or your computer through Remote Control | Monitoring or steering work while you are away from your desk |

Once the working folder, commands, and permissions make sense, moving to another interface is easy.

## What you need

For the terminal workflow, use a supported operating system, an internet connection, and an account that can access Claude Code. Current login options include Claude Pro, Max, Team, and Enterprise plans, Claude Console credits, and supported enterprise cloud providers.

The free Claude.ai plan does not include Claude Code, so check access before planning around it. You need a paid plan, Console credits, or access through a supported enterprise provider.

Check the [official quickstart](https://code.claude.com/docs/en/quickstart) and [setup requirements](https://code.claude.com/docs/en/setup) before installing, as plans and supported systems change. [Installing Claude Code](/blog/ai-tools/installing-claude-code-five-minutes) covers the current native installer, which no longer needs Node.js.

## How I use it on this site

I use Claude Code across this site, from CSS and PHP to the build process, content, and configuration.

I decide what the site needs, provide the context, and review the result. The writing starts from my notes, recordings, and rough drafts. Claude can help edit and implement, but the decision about what belongs on the site remains mine.

You do not need to know every implementation detail before starting, but you do need to recognize whether the result solves your problem.

## Start with one safe task

Open a folder that contains a project you can restore. If it is code, commit or copy it first. Then ask:

```text
Explain what is in this folder. Do not change any files.
```

Read the answer and ask where the main entry point is. You can then see what it understood before giving it permission to change anything.

The next guide opens the terminal and gets you into the right project folder.