← All posts
  • #tutorial
  • #getting-started
  • #macos
  • #installation

Setting up MOLTamp on macOS — the first 10 minutes

· · 5 min read

Download to first running session in under 10 minutes, with screenshots and the gotchas nobody tells you about.

Setting up MOLTamp on macOS — the first 10 minutes

This is the bare minimum guide to getting from "I have heard of MOLTamp" to "Claude Code is running inside a beautifully skinned terminal on my Mac." Should take about ten minutes, including the parts where you wait for the download.

Step 1: Download

Grab the latest build from moltamp.com. It is a standard .dmg for macOS. As of this writing, MOLTamp is in private beta — if you do not have early access yet, request it from the homepage and we will send you a key.

The download is around 90MB. While it is downloading, make sure you have Claude Code (or your preferred AI terminal) installed and on your $PATH. If you can run claude --version in a regular terminal and get a response, you are good.

Step 2: Install

Open the .dmg, drag MOLTamp to your Applications folder. Do not run it from inside the dmg.

The first time you launch MOLTamp from Applications, macOS will complain about it being from an unidentified developer. We are working on full notarization but it is not done yet. Right-click the app icon, choose "Open" instead of double-clicking, and confirm in the dialog. After the first launch macOS remembers the choice and you can launch normally.

Step 3: Permissions

On first launch MOLTamp will ask for a few macOS permissions. The reasons are:

  • Calendar access — only if you want to use the Calendar widget. Optional. You can deny and the rest of the app still works.
  • Microphone access — only if you plan to use the Visualizer with mic input. Almost everyone uses system audio instead, so deny is fine.
  • Apple Events — used for music player integration (Spotify, Apple Music). Deny if you do not want the music widget.
  • Screen recording — used by the Visualizer to capture system audio (this is the only API on macOS that gives you the audio stream). Deny if you do not use visualizers.

You can change all of these later in System Settings → Privacy & Security. Nothing breaks if you deny everything — it just means the corresponding widgets will be inert.

Step 4: Point at your AI terminal

MOLTamp asks where Claude Code lives the first time you open the app. The default path is /usr/local/bin/claude or /opt/homebrew/bin/claude depending on how you installed it. If you installed Claude Code via the official installer, the default should work and you can just hit confirm.

If you have a custom install location, click Browse and point at the binary. MOLTamp will remember it.

If you use Codex CLI, Gemini CLI, or Aider instead of (or in addition to) Claude Code, you can configure them under Settings → Agents. MOLTamp supports multiple agents and you can switch between them with a keyboard shortcut.

Step 5: Pick a skin

Once Claude Code is wired up, you land on the main screen — the cockpit. By default it uses the Obsidian skin. To try something else, hit the skin button in the top-right or open Settings → Skins. The bundled skin browser shows all 13 skins that ship with MOLTamp, plus any community skins you have installed.

Click any skin to apply it instantly. No restart. The whole UI re-renders with the new colors, fonts, and effects.

If you want more options, the community gallery has dozens of user-built skins. Click any one to install — MOLTamp downloads it directly into ~/Moltamp/skins/.

Step 6: Run Claude Code

This is the part where you actually use the thing. Click the terminal area, type claude, hit enter. Claude Code launches inside MOLTamp exactly as it would in any other terminal. Same prompt, same /help, same everything. Try typing a real prompt — tell me what files are in this directory and what they do. Watch the output render in your chosen skin.

If the output looks ugly in your current skin (maybe the bright colors are too bright, maybe the contrast is off), that is normal. Try a different skin. Or build your own — see Building your first MOLTamp skin for the 30-minute version.

Common gotchas

  • Claude Code asks for permission on first run — that is normal Claude Code behavior, not a MOLTamp issue. Approve the path it wants and it will not ask again.
  • The terminal looks empty / nothing happens when I type — make sure the terminal area has focus. Click directly in it. If still nothing, check that the binary path you gave MOLTamp actually points at a working executable (claude --version should work in a system terminal).
  • My fonts look weird — MOLTamp uses your system's installed fonts. If a skin asks for "JetBrains Mono" and you do not have it installed, it falls back to the next available monospace. Install JetBrains Mono if you want skins that ask for it to look right.
  • Microphone permission keeps coming back — known macOS bug, not specific to MOLTamp. Reset under System Settings → Privacy & Security → Microphone.

What to try next

Once you have Claude Code running inside MOLTamp, the rest is exploration. Try the layout editor. Drop in some widgets. Add a music player. Pick vibes art. Customize the colors of any built-in skin via Settings → Skins → Customize. Build your own skin. Browse the community.

The whole thing is designed to feel like a workspace, not a tool. The more time you spend setting it up to match your taste, the more you will want to be in it.