Skip to main content
The logout command removes your stored authentication credentials and logs you out of Sher.

Usage

sher logout

What Happens

When you run sher logout:
  1. Your auth token is removed from ~/.sher/auth.json
  2. You’re logged out locally
  3. Future sher link commands will run as anonymous (1 link/day limit)
  4. You can no longer use sher list or sher delete
Logging out does NOT delete your existing deployments. They will continue to be accessible until they expire.

Example

sher logout
  Logged out. Was logged in as octocat.

When Not Logged In

If you’re not currently logged in:
sher logout
  Not logged in.

What Gets Removed

  • Authentication token: Deleted from ~/.sher/auth.json
  • Local credentials: All stored auth data is removed

What Stays

  • Existing deployments: Your deployed links remain active until they expire
  • GitHub authorization: The OAuth connection remains in your GitHub settings (you can manually revoke it)

Effects of Logging Out

After logging out, you’ll be downgraded to Anonymous tier:
FeatureAnonymousStarter (Free)
Links per day125
Max upload size10MB50MB
Max TTL6 hours24 hours
List deployments
Delete deployments

Use Cases

Switch accounts

sher logout
sher login

Revoke access

If you want to stop using Sher or remove access:
sher logout
Then manually revoke the OAuth app in your GitHub settings.

Troubleshoot authentication

If you’re having auth issues:
sher logout
sher login

Re-authenticating

To log back in after logging out:
sher login
Your deployments are tied to your account, not your local session. Logging out and back in won’t affect your existing links.

Security

Logging out:
  • Removes the token from your local machine
  • Does NOT revoke the OAuth token on GitHub’s side
  • Does NOT delete your deployments
To fully revoke access:
  1. Run sher logout
  2. Visit GitHub Settings → Applications
  3. Find “Sher” and click “Revoke”

Build docs developers (and LLMs) love