Skip to main content

​
Install

Download the installer from claude.com/product/claude-science and double-click to install. On first launch, the app sets up its runtime and starter Python and R environments, which takes a few minutes, then opens a new tab in your default browser. If no browser tab appears, choose Open from the menu bar icon.
Claude Science is a local application, not a website, so there’s no public URL to visit. On Windows it opens in its own window, and on macOS and Linux it opens in a browser tab. Open it from the application itself: the menu bar icon on macOS, the Start menu on Windows, or the claude-science command on Linux. On a remote server, the sign-in link reaches your browser through an SSH tunnel; see Run on a remote Linux server.

​
Sign in and complete setup

When the app opens, sign in with your Claude account. On Windows, click the Sign in on the web button and confirm with Continue; the app opens claude.ai in your default browser and continues in the app window once you approve the sign-in there. If the sign-in redirect can’t return to the app (for example, through an SSH tunnel), use the Paste code instead option on the sign-in screen. No API key is required. After sign-in, a setup wizard walks you through enabling connectors and skills, setting which websites Claude can access, and choosing whether memory is on. You can change these at any time in Settings.
Claude Science keeps your data in a single folder in your home directory: ~/.claude-science on macOS and Linux, and %USERPROFILE%\.claude-science on Windows. On Linux, the claude-science command itself installs to ~/.local/bin, and on Windows the app installs to %LOCALAPPDATA%\Programs\ClaudeScience and adds that folder to your user PATH. Beyond that, it doesn’t modify your existing conda installation, R libraries, or shell configuration.
Deleting the data folder removes all projects, artifacts, and conversation history. Deleting the folder and the application removes Claude Science entirely; on Windows, quit the app from its notification-area icon, then uninstall it from Settings > Apps > Installed apps.

​
Run your first analysis

  • Open the Example project, or create a new one.
  • Start a conversation. Reference a folder on your computer by typing its path or using the @ picker in the composer.
  • Review the folder-access card when it appears and choose whether to allow it.
  • Review the code-execution card when Claude proposes running code and choose whether to allow it.
  • Results appear as artifacts in the Files panel.

​
Troubleshooting first launch

  • macOS says the application isn’t supported, or the app icon appears crossed out: the download page picked the build for the wrong processor. Return to the download page and choose Mac (Intel) or Mac (Apple Silicon) to match your Mac. To check which you have, open the Apple menu, choose About This Mac, and look at the Chip or Processor line.
  • No browser tab appeared on macOS or Linux: on macOS, choose Open from the menu bar icon. On Linux, copy the printed URL into a browser on the same machine, or run claude-science url to print a fresh one.
  • On macOS, some of Claude’s tools can’t start and the error mentions the Xcode license, usually right after an Xcode update: macOS won’t run the Python that comes with Apple’s developer tools until the license is accepted. Open Xcode and agree to the license with an administrator account, or run sudo xcodebuild -license accept in Terminal, then ask Claude to try again.
  • A Claude Science message on Windows says the app was not installed because the file could not be confirmed: the copy you opened still runs but isn’t installed. Download the installer again from claude.com/product/claude-science and open the new file. If the message persists, the PC could not verify the publisher’s signature, so ask your IT team.
  • The Windows app reports that it couldn’t set up the app window engine: the first launch downloads that engine from downloads.claude.ai, and this usually means the app couldn’t reach it. Check the internet connection, and on a corporate network ask IT to allow that domain (see Network requirements).
  • Linux refuses to start: a sandbox dependency is missing (install bubblewrap and socat as shown in the Install section), too old, or blocked. Check your bubblewrap version with bwrap --version, then match the error message to its fix in the Linux troubleshooting table.
  • Projects from another computer don’t appear: by design, Claude Science keeps your work on the computer where it’s installed, so each computer starts with its own projects. Your earlier projects are still on the other computer. See Use Claude Science on more than one computer.
  • Projects you created under another sign-in on this computer don’t appear automatically, for example, after you move from a personal plan to your organization’s Team plan: your earlier projects are still in that sign-in’s folder. Select the Review button on the banner at the top of the home screen, or select Review next to Access previously saved Claude Science work on this computer under Settings > General > Account, to access them. On Team and Enterprise plans, if there’s no banner and the setting is grayed out, your admin controls it. See Access work from another sign-in on your computer.
  • Sign-in stops at claude.ai: your account is on the Free plan (upgrade required), the redirect couldn’t return (use Paste a code), or your Team or Enterprise organization hasn’t enabled Claude Science yet.