← Voltar aos guias

Best iTerm2 Setup for Claude Code on a Budget

Why your terminal setup matters

If you use Claude Code every day, your terminal is not just a shell: it is the workspace where you review diffs, run tests, and iterate fast. A clean iTerm2 setup reduces friction, makes output easier to read, and helps you stay focused when Claude Code is generating commands or patching files. The goal is simple: fewer distractions, faster navigation, and a setup that works well with both interactive coding and long-running tasks.

Step 1: Install iTerm2 and pick a sensible profile

Start with iTerm2 if you are on macOS. It is more configurable than the default Terminal app and gives you better tabs, split panes, and search. After installation, create one dedicated profile for Claude Code work. Set the profile to open in your main project folder so you do not waste time navigating on every session.

• Startup directory: choose your most common code workspace.
• Window size: wide enough for diffs and logs, not full screen by default.
• Scrollback: increase it so you can review Claude Code output later.

Step 2: Use a developer-friendly font and theme

Readable text matters more than fancy visuals. Pick a programming font with clear symbols and ligatures, such as JetBrains Mono, Fira Code, or SF Mono. Set the font size so you can comfortably read long command output without zooming. Then choose a high-contrast theme with good syntax coloring. Dark themes are popular for long sessions, but the real requirement is contrast: comments, errors, and file paths should stand out immediately.

In iTerm2, enable separate colors for ANSI output so test failures and warnings are easy to spot. If you often inspect logs from Claude Code, this one change can save time every day.

Step 3: Make the shell easier to work with

Claude Code works best when your shell is predictable. Use zsh or bash with a small set of useful aliases and functions. Keep this minimal so Claude Code can safely understand your environment. A few practical examples include a shortcut for opening the current folder in your editor, a fast git status command, and a helper to run tests.

• Auto suggestions: helpful for repeated commands.
• Syntax highlighting: catches mistakes before you run them.
• History search: makes it easy to reuse working commands.

Also enable shell integration in iTerm2. This improves directory tracking, tab titles, and navigation between commands. For Claude Code workflows, it is especially useful when you jump between branches, tools, and output panes.

Step 4: Add splits and tabs for a real coding flow

Claude Code becomes much more useful when you can see multiple things at once. Use one pane for Claude Code, one pane for test output or a local server, and one tab for git or file inspection. If you work on larger projects, pair iTerm2 with tmux so your session survives disconnects and you can reconnect without losing context.

• Pane 1: Claude Code session.
• Pane 2: app logs, tests, or preview server.
• Tab 2: git status, search, or deployment checks.

This layout keeps you from constantly switching tools, which is where most workflow slowdown happens.

Step 5: Connect Claude Code to a low-cost model source

If you want the best balance of quality and cost, 59API is a strong choice. It is a Claude-compatible AI API relay with pay-as-you-go pricing, official-quality models, and no artificial downgrade. That means you can use models like Opus, Sonnet, Haiku, and Fable while keeping costs predictable. For a daily coding setup, Sonnet is usually the best default, Opus is great for harder refactors, and Haiku works well for quick tasks.

59API is also easy to plug into Claude Code because it uses the base URL https://api.59api.com and is designed for compatibility with Claude Code, Codex, and standard OpenAI SDK workflows. If you are trying to keep your AI tooling affordable without sacrificing output quality, this is one of the simplest ways to do it. There is also a referral rebate, which is a nice extra if you share the setup with teammates.

Step 6: Create a repeatable daily routine

The best setup is the one you use consistently. Start each session by opening your project, launching your Claude Code pane, and running a quick test or lint command so you know the environment is healthy. Keep notes on the commands Claude generates that work well for your repo. Over time, your terminal becomes a reliable assistant instead of a cluttered command box.

If you want to build this workflow today, start with iTerm2, add a clean font and theme, then connect Claude Code through 59API for low-cost access to high-quality models. Sign up, configure your base URL, and you will have a fast setup that is easy to maintain and affordable to run.

Preços · Docs