Skip to main content

Authentication

The Accomplish CLI uses OAuth 2.0 device flow for secure authentication. Your credentials are stored locally and never transmitted to third parties.

Login​

Authenticate with your Accomplish account:

acc login

The authentication process:

  1. CLI opens your default browser to the Accomplish auth page
  2. You authenticate in the browser
  3. CLI receives and stores your access token locally
  4. You're ready to use authenticated commands

Manual Authentication​

If the automatic browser opening fails, the CLI will display a URL and device code:

Visit https://accomplish.dev/auth/device and enter code ABCD-EFGH

Visit the URL manually and enter the provided code.

Check Authentication Status​

Verify your current authentication status:

acc status

This command shows:

  • Whether you're authenticated
  • Your user information
  • Token expiration status
  • Current default project (if configured)

Logout​

Sign out and remove stored credentials:

acc logout

This will:

  • Remove your stored access token
  • Clear any cached user information
  • Require re-authentication for future commands

Credential Storage​

Credentials are stored securely in your home directory:

~/.accomplish/
├── config.toml          # CLI configuration
├── default/
│   └── token            # Access token (if authenticated)
└── directories.toml     # Project directory mappings

Security Notes​

  • Tokens are stored with restricted file permissions (600)
  • No sensitive information is transmitted in plain text
  • Tokens automatically refresh when needed
  • Logout immediately invalidates stored tokens

Configuration​

The CLI uses configuration stored in ~/.accomplish/config.toml.

Troubleshooting​

Authentication Failed​

# Clear stored credentials and try again
acc logout
acc login

Browser Issues​

  • Ensure your default browser is set correctly
  • Try copying the authentication URL manually
  • Check that JavaScript is enabled in your browser

Network Issues​

  • Verify internet connectivity
  • Check firewall settings for https://accomplish.dev
  • If behind a corporate proxy, ensure it allows HTTPS connections

Permission Issues​

# Fix credential directory permissions
chmod 700 ~/.accomplish
chmod 600 ~/.accomplish/default/token