> ## Documentation Index
> Fetch the complete documentation index at: https://www.1password.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

## If you see "No accounts configured for use with 1Password CLI" or the SSH agent stops working on macOS 27 Golden Gate

If you updated to macOS 27 Golden Gate and the 1Password SSH agent stopped responding to SSH or Git requests, macOS may be blocking your terminal from accessing data from the 1Password app. To allow access:

1. Open **System Settings** > **Privacy & Security** > **Files & Folders**.
2. Select the app you use to run commands, like Terminal, iTerm, or Ghostty. If you use a terminal built into an editor, like Visual Studio Code or Cursor, select the editor.
3. Turn on the setting that starts with "Data shared by 1Password". The rest of the name depends on which 1Password apps you've installed.
4. Quit and reopen your terminal, then try your command again.

If you don't see the "Data shared by 1Password" setting, run a 1Password CLI or SSH command in that terminal and select **Allow** when macOS asks to access data from other apps. Then check again.

If you use more than one terminal, turn on the setting for each one.

## Create an SSH agent diagnostics report

If you're experiencing issues with how the SSH agent handles your SSH requests, you can send us an SSH diagnostics report so we can help resolve the problem.

You must use a [beta](https://support.1password.com/betas/) or nightly release of the 1Password app to create an SSH diagnostics report.

### Step 1: Set up SSH diagnostics recording

To start recording SSH diagnostics, navigate to the 1Password data directory:

<Tabs groupId="operating-systems">
  <Tab title="Mac">
    ```text theme={null}
    ~/Library/Group Containers/2BUA8C4S2C.com.1password/Library/Application Support/1Password/Data
    ```
  </Tab>

  <Tab title="Windows">
    ```text theme={null}
    %LOCALAPPDATA%\1Password
    ```
  </Tab>

  <Tab title="Linux">
    ```text theme={null}
    ~/.config/1Password
    ```
  </Tab>
</Tabs>

From this location, create a new subdirectory called `ssh-diagnostics`.

SSH diagnostics recording is now enabled.

### Step 2: Run some SSH requests

Run a few SSH requests using your preferred setup and tools to reproduce the issue you're having.

Each SSH request you run will be logged as a pair of JSON files in the `ssh-diagnostics` directory.

### Step 3: Create a ZIP file of your `ssh-diagnostics` directory

After you've recorded a few SSH requests that demonstrate the issue, create a ZIP file of your `ssh-diagnostics` directory.

To stop recording, delete the `ssh-diagnostics` directory.

### Step 4: Remove personally identifiable information (PII) from the diagnostics files

The files generated during the SSH diagnostics recording may contain PII, like your OS username, Git repo names, and SSH hosts.
The 1Password app attempts to redact as much of this data as possible and you'll see things like `<redacted:username>`, `<redacted:git-repo>`, and `<redacted:host>` in the generated JSON files.

However, there could still be some PII contained in your diagnostics files. Make sure to check for any information you don't want to include, like a company name that appears as part of a path, and redact it. Then recreate your ZIP file.

## Learn more

* [Autofill public keys](/ssh/public-key-autofill/)
* [Manage SSH keys](/ssh/manage-keys/#generate-an-ssh-key)
* [Sign Git commits](/ssh/git-commit-signing)
* [Workflow: Secure your SSH & Git workflows](/get-started/secure-ssh-git-workflows)


## Related topics

- [1Password Shell Plugins troubleshooting](/cli/shell-plugins/troubleshooting.md)
- [Use the 1Password agent hook to validate local .env files from 1Password Environments](/environments/agent-hook-validate.md)
- [Sync secrets from 1Password to AWS Secrets Manager (beta)](/environments/aws-secrets-manager.md)