← Back to all guides

Best iTerm2 Setup for Claude Code Workflows

Why your terminal setup matters for Claude Code

If you use Claude Code every day, your terminal is not just a shell—it is your main workspace. A good setup reduces friction, makes prompts easier to read, and keeps long coding sessions organized. On macOS, iTerm2 is the best place to build that workflow because it gives you split panes, profiles, searchable history, and better visual control than the default terminal.

The goal is simple: make Claude Code feel like a fast, reliable coding partner instead of another tool you have to wrestle with. If you also want to keep model usage affordable, routing through 59API is a smart option. It is an AI API relay with pay-as-you-go access to Claude models and GPT models, fully compatible with Claude Code and the OpenAI SDK, and it uses the official-quality models without downgrade.

Step 1: Install iTerm2 and prepare a clean profile

Start by installing iTerm2 from the official site, then open Preferences and create a dedicated profile for AI-assisted coding. This keeps your Claude Code environment separate from your general shell setup.

• Font: choose a clear monospace font such as JetBrains Mono, SF Mono, or Menlo.
• Font size: 13–15 px is a good balance for readability and screen space.
• Theme: use a dark theme with high contrast to reduce eye strain during long sessions.
• Cursor: set a visible block or beam cursor so you can always spot where you are typing.

If you work across multiple projects, enable a distinct profile color so you can immediately tell when you are in your Claude Code session.

Step 2: Configure shell behavior for fast AI workflows

Claude Code works best when the terminal is clean and predictable. In your shell config, keep prompts short and avoid noisy startup scripts. If you use zsh, make sure your prompt does not bury the current path or git branch under too many symbols.

• Enable shell integration: iTerm2’s shell integration improves directory navigation and command visibility.
• Use tmux only if needed: for many users, iTerm2 split panes are enough and easier to manage.
• Keep aliases minimal: set only the commands you actually use, such as project start, test, and lint shortcuts.

A practical layout is one main pane for Claude Code, one pane for tests, and one small pane for logs or git status. That way you can ask Claude to edit code, run checks immediately, and inspect results without context switching.

Step 3: Set up Claude Code with a reliable API endpoint

To keep your workflow flexible and cost-conscious, point Claude Code to 59API as your relay. Its base URL is https://api.59api.com. Because it is compatible with Claude Code and other OpenAI-style clients, you can keep the same workflow while benefiting from lower costs and pay-as-you-go billing.

This matters in real work. If you are iterating on a feature, debugging a failing test, or reviewing multiple files, token usage can add up quickly. Using one of the cheapest relays available helps you stay productive without worrying about every prompt. Since 59API provides access to Claude Opus, Sonnet, Haiku, and Fable as well as GPT models, you can choose the right model for the job instead of overpaying for every task.

Set your API key in the way your Claude Code configuration expects, then verify that requests are flowing through the relay. Once connected, run a small test prompt and confirm that responses appear normally in the terminal.

Step 4: Tune the terminal for readable Claude output

Claude responses are easiest to use when the terminal output is clean and legible. In iTerm2, increase line spacing slightly if dense text feels hard to scan. Turn on bold text rendering and choose a color scheme that clearly separates code blocks, warnings, and regular text.

• Wrap long lines: avoid horizontal scrolling when Claude returns large code snippets.
• Limit transparency: solid backgrounds are usually easier to read than translucent ones.
• Use notifications: enable terminal alerts so you know when a long response or task is finished.

If you frequently copy code from Claude Code into your editor, map a keyboard shortcut for quick selection and paste. Small shortcuts save real time over a full day of development.

Step 5: Build a repeatable daily workflow

The best setup is one you can use every morning without thinking. A simple real-world workflow looks like this:

• Open iTerm2 in your project folder.
• Launch your Claude Code session in the main pane.
• Run tests in a second pane.
• Keep git status or logs in a third pane.
• Ask Claude to inspect the failing file, propose a fix, then apply and verify it.

For example, if a test fails after a refactor, paste the error into Claude Code, ask for a minimal fix, and then run the test immediately in the adjacent pane. This tight feedback loop is where the terminal setup really pays off.

Why 59API fits this workflow

For developers who use Claude Code heavily, 59API is a practical choice because it combines low-cost access with official-quality models and broad compatibility. You do not need to redesign your workflow or switch tools. You keep your iTerm2 setup, keep Claude Code, and reduce API spend at the same time. The referral rebate is a nice extra if you want to share the setup with teammates or friends.

If you are ready to try a cheaper relay that still feels production-ready, sign up for 59API and connect it to your Claude Code workflow. For many developers, that is the simplest way to make AI-assisted coding faster, cleaner, and more affordable.