githits 0.6.4 → 0.6.6

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.
@@ -6,7 +6,7 @@
6
6
  },
7
7
  "metadata": {
8
8
  "description": "The code context layer for AI coding agents",
9
- "version": "0.6.4"
9
+ "version": "0.6.6"
10
10
  },
11
11
  "plugins": [
12
12
  {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "githits",
3
- "version": "0.6.4",
3
+ "version": "0.6.6",
4
4
  "description": "The code context layer for AI coding agents",
5
5
  "author": {
6
6
  "name": "GitHits"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "githits",
3
- "version": "0.6.4",
3
+ "version": "0.6.6",
4
4
  "description": "The code context layer for AI coding agents",
5
5
  "author": {
6
6
  "name": "GitHits"
package/README.md CHANGED
@@ -163,16 +163,31 @@ npx githits@latest login
163
163
  Browser OAuth is recommended for local development. Credentials are stored in
164
164
  the system keychain by default and refreshed automatically. Useful flags:
165
165
 
166
- - `init --no-browser` or `login --no-browser` prints a login URL for SSH, containers, or headless sessions
166
+ - `init --no-browser` or `login --no-browser` prints the login URL instead of launching a browser
167
+ - `init --port <port>` or `login --port <port>` fixes the loopback callback port
167
168
  - `login --force` re-authenticates even if you are already logged in
168
- - `login --port <port>` uses a specific local callback port
169
169
 
170
- For CI or non-interactive environments, use an API token:
170
+ The OAuth callback always listens on the machine where GitHits is running.
171
+ When GitHits runs over SSH and the browser runs locally, forward the selected
172
+ port from the browser machine:
171
173
 
172
174
  ```sh
173
- export GITHITS_API_TOKEN=ghi-your-token-here
175
+ ssh -N -L 8765:127.0.0.1:8765 user@remote-host
174
176
  ```
175
177
 
178
+ With that tunnel open, run GitHits on the remote machine using the same port:
179
+
180
+ ```sh
181
+ npx githits@latest init --no-browser --port 8765
182
+ ```
183
+
184
+ Open the URL printed by GitHits in the local browser. Replace
185
+ `user@remote-host` with the SSH destination you normally use. The same flags
186
+ work with `githits login` after setup.
187
+
188
+ Browser OAuth is interactive. For CI and other unattended environments, supply
189
+ `GITHITS_API_TOKEN` through the environment's secret manager.
190
+
176
191
  Inspect auth and runtime state with:
177
192
 
178
193
  ```sh