Getting Started with Claude — Mac Desktop App and Subscription

Series: Claude Learning Journey · Getting Started

Most people using Claude today are using the Mac desktop app with a Subscription account — the OAuth flow where you sign in with your Google or email account and the billing is handled through your Claude subscription. This is the simplest path, and it is where most new users should start. The API key path exists for developers who want programmatic access, but it is the minority use case.

This guide covers the desktop app first and the API path second, because the desktop app is what most readers will actually use.

The Claude Mac Desktop App

The desktop app is available at claude.ai and runs as a native application on macOS. It provides:

• A clean conversational interface
• File attachments and document uploads
• Code syntax highlighting and rendering
• Keyboard shortcuts and macOS integration -Conversation history that persists across sessions
• Team features if you are on a team plan

Download it from the website or search for Claude in the Mac App Store if it is listed there. Sign in with your account and you are ready.

Setting up a Subscription account

A Subscription gives you access to the most capable Claude models. Most subscription tiers include a monthly token allowance. When you sign in through the desktop app, the subscription is handled automatically — you do not manage API keys or billing tokens yourself.

1. Download Claude for Mac
2. Visit claude.ai and create an account (or sign in with Google)
3. Choose a subscription tier based on your usage needs
4. Open the desktop app and you are authenticated automatically

This is the OAuth flow. It means you are authenticating through Anthropic’s web identity system and the desktop app receives a session token rather than you handling API keys directly.

The authentication difference that matters

With a Subscription account and the desktop app, authentication is handled by the application. You do not see or manage secrets. This is conceptually similar to how you log into a web app with Google OAuth — the app receives a token, not your credentials.

With an API key, you are responsible for managing the key itself — storing it securely, rotating it, not committing it to version control, and setting usage limits on the key itself.

For most people, the Subscription + desktop app route is simpler and safer. You get on-demand access to the models without managing infrastructure.

Switching between accounts

If you have multiple accounts — a personal Subscription and a team account, for example — the desktop app supports account switching. This matters if you want to keep work and personal contexts separate.

You can sign out and sign back in, or in some versions there is a direct account switcher in the app menu. Check the app preferences if you need to manage multiple accounts.

API keys — when to use them

API key access exists for developers who want to integrate Claude into automated workflows, custom applications, or scripts. You generate a key in the Anthropic console and use it in requests to the API.

You do not need an API key if:
- You use the desktop app for conversations
- You are on a team with managed seats
- You do not need programmatic access to Claude

You do need an API key if:
- You are building an application that calls Claude
- You want to run Claude in a CI pipeline
- You need to automate tasks that are easier to script than do manually in the app
- You are building a product that uses Claude as a backend

Installing the CLI as a developer option

If you are using API keys and want command-line access (useful for scripting and CI), install the Claude CLI:

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

Once installed, provide your API key:

export ANTHROPIC_API_KEY="sk-ant-..."

Add that to your shell profile so it persists. The CLI reads the API key from the environment variable on each call.

You can verify the CLI is configured correctly:

claude -p "Reply with exactly the word 'works' if you can read this"

If you see “works”, the setup is correct.

Choosing a model

If you are on a Subscription, your available models are determined by your tier. Higher tiers unlock Opus, Sonnet, and Haiku. The desktop app lets you switch models mid-conversation, so you can use Haiku for quick tasks and switch to Sonnet or Opus when you need more reasoning capability.

With an API key, you explicitly specify the model in each API call. Sonnet 4 is the sensible default for most tasks — capable enough for complex work, fast enough for high-volume tasks, and reasonably priced. Switch to Opus when you hit capability limits.

Checking your setup

If you are on the desktop app, there is nothing to check — if the app loads and you can send messages, you are set up correctly.

If you are using the CLI with an API key, run the verification command above. If it returns “works”, your API key is valid and your network can reach Anthropic.

Try it yourself

Download the desktop app, sign in, and start a conversation. Ask Claude something you actually want to know — explain a technical concept, draft part of an email, or ask about a tool or framework you are evaluating. Form your own view of whether this is useful.

What’s Next

A conversation is only as good as what you bring to it. The next post covers what actually happens in a session and how to structure your first real interaction with Claude.

Part of the Claude Learning Journey series · Next: Your First Agent Session