openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-21 19:25:25 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

[PR #166] [MERGED] fix(cli): clarify logout only affects local config #278

New Issue
Closed
opened 2026-02-15 17:16:38 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:16:38 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/openclaw/clawhub/pull/166
Author: @aronchick
Created: 2/7/2026
Status: ✅ Merged
Merged: 2/14/2026
Merged by: @steipete

Base: main ← Head: fix/clarify-logout-scope

📝 Commits (4)

  • 6b3ccfd fix(cli): clarify logout only affects local config
  • 1082820 fix(cli): clarify logout revocation scope (#166) (thanks @aronchick)
  • 3714ad4 chore: sync changelog for merge (#166) (thanks @aronchick)
  • 639a3cb merge: update branch from main for PR #166

📊 Changes

3 files changed (+68 additions, -1 deletions)

View changed files

📝 CHANGELOG.md (+1 -0)
➕ packages/clawdhub/src/cli/commands/auth.test.ts (+66 -0)
📝 packages/clawdhub/src/cli/commands/auth.ts (+1 -1)

📄 Description

Problem

clawhub logout says 'OK. Logged out.' but the token remains valid on the server until explicitly revoked. Users on shared machines may think they're fully logged out when they're not.

Solution

Update message to clarify:

  • Logout is local only
  • Token remains valid until revoked in web UI

Changes

  • packages/clawdhub/src/cli/commands/auth.ts: Update logout message

Before/After

Before: OK. Logged out.
After: Logged out locally. Token still valid until revoked at clawhub.io/settings

Greptile Overview

Greptile Summary

This PR updates the clawhub logout CLI output to clarify that logging out only clears the locally stored token/config and does not revoke the token on the server; users must revoke the token separately via the settings page.

The change is isolated to packages/clawdhub/src/cli/commands/auth.ts and does not affect authentication logic or token storage—only the user-facing message printed after logout.

Confidence Score: 5/5

  • This PR is safe to merge with minimal risk.
  • Single-line change to a console message; no behavior, control flow, or API interaction changes. Reviewed the modified file and verified the logout command still only updates local config as intended.
  • No files require special attention

(5/5) You can turn off certain types of comments like style here!

Context used:

  • Context from dashboard - AGENTS.md (source)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/openclaw/clawhub/pull/166 **Author:** [@aronchick](https://github.com/aronchick) **Created:** 2/7/2026 **Status:** ✅ Merged **Merged:** 2/14/2026 **Merged by:** [@steipete](https://github.com/steipete) **Base:** `main` ← **Head:** `fix/clarify-logout-scope` --- ### 📝 Commits (4) - [`6b3ccfd`](https://github.com/openclaw/clawhub/commit/6b3ccfd4a065f07df402d8c5b3c896ee5d46802e) fix(cli): clarify logout only affects local config - [`1082820`](https://github.com/openclaw/clawhub/commit/10828209ee0b737f3ef41e1caed89f0d913c8b92) fix(cli): clarify logout revocation scope (#166) (thanks @aronchick) - [`3714ad4`](https://github.com/openclaw/clawhub/commit/3714ad4cb923fb72660a39fc2669909e5cf1cb5c) chore: sync changelog for merge (#166) (thanks @aronchick) - [`639a3cb`](https://github.com/openclaw/clawhub/commit/639a3cbb0e243cb7e46f2212bf7e3a9018f3b423) merge: update branch from main for PR #166 ### 📊 Changes **3 files changed** (+68 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.md` (+1 -0) ➕ `packages/clawdhub/src/cli/commands/auth.test.ts` (+66 -0) 📝 `packages/clawdhub/src/cli/commands/auth.ts` (+1 -1) </details> ### 📄 Description ## Problem `clawhub logout` says 'OK. Logged out.' but the token remains valid on the server until explicitly revoked. Users on shared machines may think they're fully logged out when they're not. ## Solution Update message to clarify: - Logout is local only - Token remains valid until revoked in web UI ## Changes - `packages/clawdhub/src/cli/commands/auth.ts`: Update logout message ## Before/After **Before:** `OK. Logged out.` **After:** `Logged out locally. Token still valid until revoked at clawhub.io/settings` <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates the `clawhub logout` CLI output to clarify that logging out only clears the locally stored token/config and does not revoke the token on the server; users must revoke the token separately via the settings page. The change is isolated to `packages/clawdhub/src/cli/commands/auth.ts` and does not affect authentication logic or token storage—only the user-facing message printed after logout. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk. - Single-line change to a console message; no behavior, control flow, or API interaction changes. Reviewed the modified file and verified the logout command still only updates local config as intended. - No files require special attention <!-- greptile_other_comments_section --> <sub>(5/5) You can turn off certain types of comments like style [here](https://app.greptile.com/review/github)!</sub> **Context used:** - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=a1d58d20-b4dd-4cbb-973a-9fd7824e1921)) <!-- /greptile_comment --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 17:16:38 -05:00
yindo closed this issue 2026-02-15 17:16:38 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#278
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?