@ariobarin/glossa 0.1.0-beta.11 → 0.1.0-beta.12
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 +17 -7
- package/dist/app.js +3169 -2029
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -24,26 +24,36 @@ macOS or Linux:
|
|
|
24
24
|
curl -fsSL https://glossa.sh/install.sh | sh
|
|
25
25
|
```
|
|
26
26
|
|
|
27
|
-
Open a terminal in the
|
|
27
|
+
Open a terminal in the directory you want to expose, then run:
|
|
28
28
|
|
|
29
29
|
```shell
|
|
30
30
|
glossa
|
|
31
31
|
```
|
|
32
32
|
|
|
33
33
|
The hosted commands run the tracked scripts in `site`. They verify native
|
|
34
|
-
release checksums before installing.
|
|
35
|
-
installation method.
|
|
34
|
+
release checksums before installing. Stop every running Glossa session, then
|
|
35
|
+
rerun the original installation method to update Glossa.
|
|
36
36
|
|
|
37
37
|
Glossa opens Google sign-in automatically when needed using OAuth Device Authorization Flow. Public client and resource identifiers are built in, so testers do not configure OAuth values. Use the same Google account when authorizing Glossa in ChatGPT.
|
|
38
38
|
|
|
39
39
|
OAuth and device credentials use the operating-system credential store. If it is unavailable, Glossa warns before using a restricted credential file.
|
|
40
40
|
|
|
41
|
-
Glossa signs in automatically and exposes the current
|
|
41
|
+
Glossa signs in automatically and exposes the current directory. Pass a directory
|
|
42
|
+
to expose a different workspace. The responsive terminal interface shows the
|
|
43
|
+
workspace, device, and current connection or tool status.
|
|
42
44
|
|
|
43
|
-
|
|
45
|
+
Press `d` for compact tool history, `s` for account and device status, or `?`
|
|
46
|
+
for help. The activity view shows each local tool name and a compact form of its
|
|
47
|
+
input. Press `q` or Ctrl+C to disconnect.
|
|
44
48
|
|
|
45
|
-
|
|
49
|
+
Connected clients can modify files inside the exposed workspace and run commands
|
|
50
|
+
with the full environment and permissions of the operating-system account that
|
|
51
|
+
launched Glossa.
|
|
52
|
+
|
|
53
|
+
Use `glossa status` to show the signed-in account, relay, devices, and active
|
|
54
|
+
workspaces. Use `glossa devices revoke <id>` to revoke a device. Use
|
|
55
|
+
`glossa logout` to remove local OAuth credentials and open browser sign-out.
|
|
46
56
|
|
|
47
57
|
The managed endpoint defaults to `https://mcp.glossa.sh`. Development deployments may override `GLOSSA_RELAY_ORIGIN` and `GLOSSA_WORKER_ORIGIN`. Plain HTTP is accepted only for loopback relay origins and loopback or private IPv4 worker origins.
|
|
48
58
|
|
|
49
|
-
|
|
59
|
+
Other running Glossa sessions remain connected until stopped or revoked.
|