claude_profile 1.2.0

Claude Code account credential management and token status
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108

# Test: `.token.status`

Integration test planning for the `.token.status` command. See [command/namespace.md](../../../../docs/cli/command/005_token.md#command--7-tokenstatus) for specification.

### Test Case Index

| ID | Test Name | Category |
|----|-----------|----------|
| IT-1 | Valid token shows "valid" with remaining time | Basic Invocation |
| IT-2 | Expired token shows "expired" | Status Classification |
| IT-3 | ExpiringSoon token shows "expiring soon" with remaining time | Status Classification |
| IT-4 | Custom `threshold::1800` changes classification boundary | Threshold Override |
| IT-5 | `threshold::0` never classifies as ExpiringSoon | Threshold Edge |
| IT-6 | `format::json` returns JSON object with status and expires_in_secs | Output Format |
| IT-8 | Missing credentials file exits 2 | Error Handling |
| IT-9 | Credentials file with unparseable `expiresAt` exits 2 | Error Handling |

### Test Coverage Summary

- Basic Invocation: 1 test
- Status Classification: 2 tests
- Threshold Override: 1 test
- Threshold Edge: 1 test
- Output Format: 1 test
- Error Handling: 2 tests

**Total:** 8 integration tests

---

### IT-1: Valid token shows "valid" with remaining time

- **Given:** `~/.claude/.credentials.json` contains an `expiresAt` timestamp set to current time + 7200 seconds (2 hours from now). Default threshold is 3600 seconds.
- **When:** `clp .token.status`
- **Then:** Output on stdout matching pattern `valid — *remaining` (e.g., `valid — 1h59m remaining`), exit 0.; output contains "valid" and remaining time
- **Exit:** 0
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)

---

### IT-2: Expired token shows "expired"

- **Given:** `~/.claude/.credentials.json` contains an `expiresAt` timestamp set to current time - 3600 seconds (1 hour ago).
- **When:** `clp .token.status`
- **Then:** Output on stdout containing `expired`, exit 0.; output contains "expired"
- **Exit:** 0
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)

---

### IT-3: ExpiringSoon token shows "expiring soon" with remaining time

- **Given:** `~/.claude/.credentials.json` contains an `expiresAt` timestamp set to current time + 1800 seconds (30 minutes from now). Default threshold is 3600 seconds, so 1800 < 3600 triggers ExpiringSoon.
- **When:** `clp .token.status`
- **Then:** Output on stdout matching pattern `expiring soon — *remaining` (e.g., `expiring soon — 29m remaining`), exit 0.; output contains "expiring soon" and remaining time
- **Exit:** 0
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)

---

### IT-4: Custom threshold changes classification boundary

- **Given:** `~/.claude/.credentials.json` contains an `expiresAt` timestamp set to current time + 2500 seconds. With default threshold (3600), this would be "expiring soon". With threshold 1800, it should be "valid".
- **When:** `clp .token.status threshold::1800`
- **Then:** Output on stdout containing `valid`, exit 0.; output contains "valid" under custom threshold
- **Exit:** 0
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)

---

### IT-5: Threshold zero never classifies as ExpiringSoon

- **Given:** `~/.claude/.credentials.json` contains an `expiresAt` timestamp set to current time + 60 seconds (1 minute remaining). With default threshold (3600), this would be "expiring soon".
- **When:** `clp .token.status threshold::0`
- **Then:** Output on stdout containing `valid`, exit 0.; output contains "valid" even with very little time remaining
- **Exit:** 0
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)

---

### IT-6: JSON format returns structured object

- **Given:** `~/.claude/.credentials.json` contains an `expiresAt` timestamp set to current time + 7200 seconds.
- **When:** `clp .token.status format::json`
- **Then:** Valid JSON on stdout (e.g., `{"status":"valid","expires_in_secs":7199}`), exit 0.; output is valid JSON with `status` and `expires_in_secs` keys
- **Exit:** 0
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)

---

### IT-8: Missing credentials file exits 2

- **Given:** Ensure `~/.claude/.credentials.json` does not exist (rename or remove it). Account store state is irrelevant.
- **When:** `clp .token.status`
- **Then:** Error message on stderr indicating credentials file is unreadable or missing, exit 2.; stderr contains error about missing credentials
- **Exit:** 2
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)

---

### IT-9: Unparseable `expiresAt` exits 2

- **Given:** `~/.claude/.credentials.json` contains valid JSON but with `"expiresAt": "not-a-timestamp"` (a non-numeric, non-ISO string).
- **When:** `clp .token.status`
- **Then:** Error message on stderr indicating `expiresAt` is unparseable, exit 2.; stderr contains error about unparseable expiresAt
- **Exit:** 2
- **Source:** [command/005_token.md — .token.status](../../../../docs/cli/command/005_token.md#command--7-tokenstatus)