@lotics/cli 0.321.79 → 0.321.81
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/AGENTS.md +3 -3
- package/README.md +6 -13
- package/dist/src/cli.js +17 -124
- package/docs/cli_reference.md +3 -4
- package/docs/design.md +2 -2
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -58,10 +58,10 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
|
|
|
58
58
|
and then re-running what you wanted. Never wrap it in a timeout waiting for a human — `--wait`
|
|
59
59
|
exists if you really want one blocking command, and killing that one is safe too (the request
|
|
60
60
|
survives and the next command claims it). A command run before Confirm exits 1 naming the page and
|
|
61
|
-
code again; once the 15 minutes are up it says to ask again.
|
|
62
|
-
|
|
61
|
+
code again; once the 15 minutes are up it says to ask again. A person with no account creates one on
|
|
62
|
+
that page, by email or with Google, and the same press signs the terminal in.
|
|
63
63
|
- **A credential is either a SIGN-IN or an API KEY, and `logout` treats them differently.** A profile
|
|
64
|
-
from `auth login`
|
|
64
|
+
from `auth login` acts as the person who confirmed it and is theirs — `lotics auth
|
|
65
65
|
logout` revokes it server-side, and it lapses on its own after 90 idle days (each use pushes that
|
|
66
66
|
out). A profile from `auth api-key` holds a key an ADMIN issued. A key created in Settings carries
|
|
67
67
|
its OWN access — every app and table, or only the ones chosen on the key, so a listing that comes
|
package/README.md
CHANGED
|
@@ -44,11 +44,11 @@ package (reachable at `node_modules/@lotics/cli/docs/*.md` once installed):
|
|
|
44
44
|
|
|
45
45
|
## Start in two commands
|
|
46
46
|
|
|
47
|
-
Install the CLI and
|
|
47
|
+
Install the CLI and sign in, creating an account on the page the sign-in opens when you have none; the account's workspace is then built with the tools:
|
|
48
48
|
|
|
49
49
|
```bash
|
|
50
50
|
curl -fsSL https://lotics.ai/install.sh | bash
|
|
51
|
-
lotics auth
|
|
51
|
+
lotics auth login
|
|
52
52
|
```
|
|
53
53
|
|
|
54
54
|
The installer downloads one compiled executable — no Node.js, no npm: every app is deployed on
|
|
@@ -102,18 +102,11 @@ The CLI checks for updates once per day and prints a note on stderr, naming the
|
|
|
102
102
|
|
|
103
103
|
## Authentication
|
|
104
104
|
|
|
105
|
-
**Two kinds of credential, and which you hold decides what `logout` does.** `auth
|
|
105
|
+
**Two kinds of credential, and which you hold decides what `logout` does.** `auth login` gives this machine a **sign-in** — it acts as you, carries whatever role you have, and is yours to see and revoke at Settings → Security → *Keys and terminals*; it lapses after 90 days of disuse, and each use pushes that out. `auth api-key` saves an **API key** an admin issued. A key an admin creates in Settings has its own name and its own access, reaching either every app and table or only the ones chosen on the key; an older key created FOR a person carries that person's access and stops working when that person is removed. Either kind often lives on a server and on other people's machines too, and only an admin revokes it. `lotics auth whoami` prints which kind this machine holds — from the saved profile, or from the server when the profile does not say.
|
|
106
106
|
|
|
107
107
|
When a credential stops working the refusal says which of the three ways it is dead — "… was revoked." / "… expired." / "… belongs to a member who is no longer active in this organization." — and its `hint` names the remedy: `lotics auth login` for a terminal sign-in, ask an admin for a new key for an API key. A credential whose record does not say which of the two it is gets both. A key the server does not recognize at all gets one generic answer, deliberately: an unrecognized key learns nothing from being refused.
|
|
108
108
|
|
|
109
|
-
**`lotics auth
|
|
110
|
-
|
|
111
|
-
```bash
|
|
112
|
-
lotics auth signup # interactive prompts
|
|
113
|
-
lotics auth signup a@b.com --name "Agent" # non-interactive
|
|
114
|
-
```
|
|
115
|
-
|
|
116
|
-
**`lotics auth login`** — Signs in an account that already exists, on a new machine or to add another organization to one that holds a key (the one you pick becomes active). **It does not wait for you.** It takes no argument and sends no mail: it prints the page to open and the code that page must show, then exits. Sign in there if asked, check the code, pick the organization, press Confirm — and run whatever you wanted to run: the next command that needs a credential collects the key before doing its own work.
|
|
109
|
+
**`lotics auth login`** — Signs this terminal in: for the first time, on a new machine, or to add another organization to one that holds a key (the one you pick becomes active). **It does not wait for you.** It takes no argument and sends no mail: it prints the page to open and the code that page must show, then exits. Sign in there if asked, check the code, pick the organization, press Confirm — and run whatever you wanted to run: the next command that needs a credential collects the key before doing its own work. With no account, create one on that page, by email and a password or with Google: the page shows the code beside the button, and one press creates the account and its first workspace and signs the terminal in. Creating the account accepts the Terms (https://lotics.ai/terms) and the Privacy Policy (https://lotics.ai/privacy). On a private instance people arrive by invitation, and the page asks a signed-out person to sign in.
|
|
117
110
|
|
|
118
111
|
```bash
|
|
119
112
|
lotics auth login # prints the page + code, exits — nothing to keep open
|
|
@@ -126,7 +119,7 @@ lotics auth login --local # pins this directory to that org (implies
|
|
|
126
119
|
|
|
127
120
|
A command run before you press Confirm names the page and the code again and exits 1; the request is good for 15 minutes, after which the next command says to ask again. Re-running `auth login` is always safe — it replaces the request, so only the newest code is the live one.
|
|
128
121
|
|
|
129
|
-
**`lotics auth web`** — Send a magic link email to access the web app (requires
|
|
122
|
+
**`lotics auth web`** — Send a magic link email to access the web app (requires an account). If the account's email address was never confirmed and it holds a password, signing in with the link removes that password; the command says so and names where *Forgot password* sets a new one.
|
|
130
123
|
|
|
131
124
|
```bash
|
|
132
125
|
lotics auth web
|
|
@@ -139,7 +132,7 @@ lotics auth api-key # interactive prompt
|
|
|
139
132
|
lotics auth api-key ltk_... # registers the key's org as a profile (now active)
|
|
140
133
|
```
|
|
141
134
|
|
|
142
|
-
Run `lotics auth logout [<name|id>]` to remove a profile (default: the active org), or `lotics auth logout --all` to wipe the store. Inside a pinned directory the bare form removes the **pin**, not a profile — name the org to remove its credential. A profile saved by `auth login`
|
|
135
|
+
Run `lotics auth logout [<name|id>]` to remove a profile (default: the active org), or `lotics auth logout --all` to wipe the store. Inside a pinned directory the bare form removes the **pin**, not a profile — name the org to remove its credential. A profile saved by `auth login` is a **sign-in**, and logging out revokes it server-side too. One saved by `auth api-key` is an admin-issued key that other machines may also hold, so it is only removed from this machine and stays active until an admin revokes it under Settings → API keys. A profile saved before the kind was recorded states nothing, so the server is asked and the credential is revoked only if the answer is a sign-in.
|
|
143
136
|
|
|
144
137
|
## Organizations
|
|
145
138
|
|