@kimuson/claude-code-viewer 0.4.15 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -55,17 +55,30 @@ Note: Additional UI screenshots are available in [/e2e/snapshots/](./e2e/snapsho
55
55
  Run directly from npm without installation:
56
56
 
57
57
  ```bash
58
- PORT=3400 npx @kimuson/claude-code-viewer@latest
58
+ npx @kimuson/claude-code-viewer@latest --port 3400
59
59
  ```
60
60
 
61
61
  Alternatively, install globally:
62
62
 
63
63
  ```bash
64
64
  npm install -g @kimuson/claude-code-viewer
65
- claude-code-viewer
65
+ claude-code-viewer --port 3400
66
66
  ```
67
67
 
68
- The server will start on port 3400 (or your specified PORT). Open `http://localhost:3400` in your browser to access the interface.
68
+ The server will start on port 3400 (or the default port 3000). Open `http://localhost:3400` in your browser to access the interface.
69
+
70
+ **Available Options:**
71
+
72
+ ```bash
73
+ claude-code-viewer [options]
74
+
75
+ Options:
76
+ -p, --port <port> Port to listen on (default: 3000)
77
+ -h, --hostname <hostname> Hostname to listen on (default: localhost)
78
+ -P, --password <password> Password for authentication
79
+ -e, --executable <executable> Path to Claude Code executable
80
+ --claude-dir <claude-dir> Path to Claude directory
81
+ ```
69
82
 
70
83
  ### Docker Deployment
71
84
 
@@ -79,7 +92,8 @@ Run the container directly:
79
92
 
80
93
  ```bash
81
94
  docker run --rm -p 3400:3400 \
82
- -e CLAUDE_CODE_VIEWER_AUTH_PASSWORD=your-password \
95
+ -e PORT=3400 \
96
+ -e CCV_PASSWORD=your-password \
83
97
  -e ANTHROPIC_BASE_URL=... \
84
98
  -e ANTHROPIC_API_KEY=... \
85
99
  -e ANTHROPIC_AUTH_TOKEN=... \
@@ -126,15 +140,22 @@ The application reads Claude Code conversation logs from:
126
140
 
127
141
  ## Configuration
128
142
 
129
- ### Environment Variables
143
+ ### Command-Line Options and Environment Variables
130
144
 
131
- Claude Code Viewer reads several reserved environment variables. All values are optional and only need to be set if you want to override the defaults.
145
+ Claude Code Viewer can be configured using command-line options or environment variables. Command-line options take precedence over environment variables.
132
146
 
133
- | Key | Description |
134
- | --- | --- |
135
- | CLAUDE_CODE_VIEWER_CC_EXECUTABLE_PATH | Path to Claude Code installation. If not set, uses system PATH installation, or falls back to bundled version from dependencies |
136
- | CLAUDE_CODE_VIEWER_AUTH_PASSWORD | Password for authentication. When set, enables password-based authentication to protect access to Claude Code Viewer. All `/api` routes (except login, logout, check, config, and version endpoints) require authentication. If not set, authentication is disabled and the application is publicly accessible |
137
- | PORT | Port number for Claude Code Viewer to run on |
147
+ | Command-Line Option | Environment Variable | Description | Default |
148
+ | --- | --- | --- | --- |
149
+ | `-p, --port <port>` | `PORT` | Port number for Claude Code Viewer to run on | `3000` |
150
+ | `-h, --hostname <hostname>` | `HOSTNAME` | Hostname to listen on for remote access | `localhost` |
151
+ | `-P, --password <password>` | `CCV_PASSWORD` | Password for authentication. When set, enables password-based authentication to protect access to Claude Code Viewer. All `/api` routes (except login, logout, check, config, and version endpoints) require authentication. If not set, authentication is disabled and the application is publicly accessible | (none) |
152
+ | `-e, --executable <executable>` | `CCV_CC_EXECUTABLE_PATH` | Path to Claude Code installation. If not set, uses system PATH installation, or falls back to bundled version from dependencies | (auto-detect) |
153
+ | `--claude-dir <claude-dir>` | `CCV_GLOBAL_CLAUDE_DIR` | Path to Claude directory where session logs are stored | `~/.claude` |
154
+
155
+ **Breaking Change**: Environment variable names have been changed. If you're using environment variables, update them as follows:
156
+ - `CLAUDE_CODE_VIEWER_AUTH_PASSWORD` → `CCV_PASSWORD`
157
+ - `CLAUDE_CODE_VIEWER_CC_EXECUTABLE_PATH` → `CCV_CC_EXECUTABLE_PATH`
158
+ - New environment variable added: `CCV_GLOBAL_CLAUDE_DIR` (previously the Claude directory path was hardcoded to `~/.claude`)
138
159
 
139
160
  ### User Settings
140
161
 
@@ -201,7 +222,7 @@ Claude Code Viewer is designed with remote hosting in mind. To support remote de
201
222
  - **Real-time Notifications**: Audio notifications for task completion to maintain workflow awareness
202
223
  - **System Monitoring**: Monitor Claude Code compatibility and feature availability across environments
203
224
 
204
- The application features a separated client-server architecture that enables remote hosting. **Basic password authentication is available** via the `CLAUDE_CODE_VIEWER_AUTH_PASSWORD` environment variable. When set, users must authenticate with the configured password before accessing the application. However, this is a simple single-password authentication mechanism without advanced features like multi-user support, role-based access control, or OAuth integration. If you require more sophisticated authentication, carefully evaluate your security requirements and implement appropriate access controls at the infrastructure level (e.g., reverse proxy with OAuth, VPN, IP whitelisting).
225
+ The application features a separated client-server architecture that enables remote hosting. **Basic password authentication is available** via the `--password` command-line option or `CCV_PASSWORD` environment variable. When set, users must authenticate with the configured password before accessing the application. However, this is a simple single-password authentication mechanism without advanced features like multi-user support, role-based access control, or OAuth integration. If you require more sophisticated authentication, carefully evaluate your security requirements and implement appropriate access controls at the infrastructure level (e.g., reverse proxy with OAuth, VPN, IP whitelisting).
205
226
 
206
227
  ## License
207
228