​
Authentication Commands

The Arc Memory CLI provides commands for authenticating with GitHub, which is required for accessing GitHub data such as pull requests and issues. Related Documentation:

​
Overview

Authentication is handled through the arc auth command group. Arc Memory uses GitHub’s device flow for authentication, which is a secure way to authenticate without having to enter your credentials directly.

​
Commands

​
arc auth gh

Authenticate with GitHub using device flow. 
arc auth gh [OPTIONS]
This command initiates the GitHub device flow authentication process. It will display a code and a URL. You need to visit the URL, enter the code, and authorize the Arc Memory application to access your GitHub account.

​
Options

  • --client-id TEXT: GitHub OAuth client ID. If not provided, uses the default Arc Memory app.
  • --client-secret TEXT: GitHub OAuth client secret. If not provided, uses the default Arc Memory app.
  • --timeout INTEGER: Timeout in seconds for the device flow (default: 300).
  • --debug: Enable debug logging.

​
Example

# Authenticate with GitHub using the default Arc Memory app
arc auth gh

# Authenticate with a custom GitHub OAuth app
arc auth gh --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET

# Authenticate with a longer timeout
arc auth gh --timeout 600

​
arc auth gh-app

Authenticate with a GitHub App. 
arc auth gh-app [OPTIONS]
This command configures authentication for a GitHub App. GitHub Apps provide more granular permissions and can be installed on organizations.

​
Options

  • --app-id TEXT: GitHub App ID.
  • --private-key TEXT: Path to the GitHub App private key file.
  • --client-id TEXT: GitHub OAuth client ID for the GitHub App.
  • --client-secret TEXT: GitHub OAuth client secret for the GitHub App.
  • --debug: Enable debug logging.

​
Example

# Authenticate with a GitHub App
arc auth gh-app --app-id 12345 --private-key path/to/private-key.pem

​
Authentication Storage

Arc Memory stores authentication tokens securely:
  1. System Keyring: By default, tokens are stored in your system’s secure keyring (Keychain on macOS, Credential Manager on Windows, etc.).
  2. Environment Variables: You can also provide tokens via environment variables (GITHUB_TOKEN).
If a token is found in environment variables, Arc Memory will ask if you want to store it in the system keyring for future use.

​
Checking Authentication Status

You can verify your authentication status by running: 
arc doctor
This will show if you have a valid GitHub token configured.

​
Troubleshooting

​
Authentication Failures

If you encounter authentication issues:
  1. Network Issues:
    • Check your internet connection
    • Ensure you can access github.com in your browser
    • If behind a corporate firewall, check if GitHub API access is allowed
    • Try again with arc auth gh --debug to see detailed error messages
  2. Token Expiration:
    • GitHub tokens can expire or be revoked
    • Simply run arc auth gh again to get a new token
    • You’ll see a new device code and URL to visit
  3. Permission Issues:
    • Ensure the token has the necessary permissions (repo, read:org)
    • If you’re using a custom client ID, verify it has the correct scopes
    • You may need to revoke the existing token in your GitHub settings and re-authenticate
  4. Rate Limiting:
    • GitHub API has rate limits
    • If you hit them, wait or use a token with higher limits
    • Enterprise accounts typically have higher rate limits

​
Re-authentication

You may need to re-authenticate in these situations:
  1. New Device: When using Arc Memory on a new device
  2. Token Revoked: If you revoked the token in GitHub settings
  3. Token Expired: If your token has expired
  4. Permission Changes: If you need different permissions
To re-authenticate: 
# Simple re-authentication
arc auth gh

# Force re-authentication even if a token exists
arc auth gh --force  # Note: The --force flag is conceptual and may not be implemented yet

# Re-authenticate with debug logging
arc auth gh --debug

​
Verifying Authentication

To verify that your authentication is working: 
# Check your authentication status
arc doctor

# Try building the graph to verify GitHub API access
arc build
If you see GitHub data in your graph, your authentication is working correctly.