# Claude Code: My First Hands-on Experience

> Source: <https://promptcube3.com/en/threads/2933/>
> Published: 2026-07-24 22:04:20+00:00

# Claude Code: My First Hands-on Experience

[Claude](/en/tags/claude/)Code is essentially a terminal-resident LLM agent that doesn't just suggest code but actually executes it, runs tests, and manages your git flow. Unlike a standard chat interface where you copy-paste errors back and forth, this tool operates directly on your file system with a loop of "plan → execute → verify."

## Setting Up the Environment

Getting this running requires a few specific prerequisites. You can't just install it via a standard package manager without the right environment. I found that using the latest Node.js LTS is mandatory to avoid dependency conflicts during the initial handshake.

To get started from scratch, run the following command in your terminal:

```
npm install -g @anthropic-ai/claude-code
```

Once installed, you need to authenticate. Run `claude`

and it will trigger an OAuth flow. The critical part here is ensuring your CLI has the necessary permissions to read/write to your project directory, otherwise, the agent will hallucinate that it changed a file when it actually failed silently due to permission errors.

## Real-World Workflow: Bug Fixing and Refactoring

I tested this on a legacy TypeScript project with a messy set of utility functions. Instead of manually searching for the bug, I gave it a high-level objective: "Find why the date formatter is offsetting by 24 hours in UTC-5 and fix it."

The agent didn't just guess. It performed the following sequence:

1. Used `grep`

to find all instances of `Date.utcOffset`

.

2. Read the specific file `src/utils/dateHelper.ts`

.

3. Created a temporary test file `test-fix.ts`

to reproduce the bug.

4. Ran the test using `npm test`

, saw it fail, applied the fix, and ran it again until it passed.

Here is an example of the kind of command-line interaction it handles internally:

```
# The agent executes this to verify its own fix
npm test src/utils/dateHelper.test.ts -- --grep "UTC Offset"
```

## Performance and Practical Constraints

While the agent is powerful, there are a few technical nuances you need to be aware of regarding token usage and context windows.

**Context Management:** Claude Code indexes your local files. If you have a massive`node_modules`

folder or a`.git`

directory that isn't ignored, the agent can get bogged down. I highly recommend having a strict`.gitignore`

because the tool respects it to prune the context.**Execution Speed:** The "think" loop takes a few seconds per step. It's not instantaneous.**Token Cost:** Since it reads multiple files to build a mental map of your architecture, a single complex task can consume a surprising amount of tokens compared to a simple prompt in a web UI.

## Comparison: Claude Code vs. Cursor

I've used both, and the difference is fundamental. Cursor is an IDE with AI integrated; Claude Code is an AI agent that uses the terminal.

**Interface:** Cursor is GUI-based; Claude Code is CLI-based.**Agency:** Cursor is better for writing new blocks of code; Claude Code is significantly better for "maintenance" tasks (e.g., "Update all deprecated API calls in the project to the new version").**Integration:** Cursor manages the editor; Claude Code manages the shell, including running build scripts and managing git commits.

For anyone looking to automate the boring parts of a deployment or a large-scale refactor, this is a massive step up from standard prompt engineering. It turns the LLM into a junior developer who actually knows how to use a terminal.

[Next Google Zero: The End of the Search Traffic Era →](/en/threads/2920/)