@jaato/web-coder-ui 0.1.0 → 0.1.2
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
|
@@ -64,6 +64,29 @@ The token is only ever handed to the page on a loopback bind: with
|
|
|
64
64
|
person at the browser types the token. On loopback the `Host` header must
|
|
65
65
|
name the bound address, so a DNS-rebinding page cannot fetch it either.
|
|
66
66
|
|
|
67
|
+
### Signing in from the prompt
|
|
68
|
+
|
|
69
|
+
Nothing has to be configured before the first session, exactly as in the
|
|
70
|
+
TUI. Connect, and the "New session" card offers three ways in: an agent
|
|
71
|
+
profile, the workspace defaults (`JAATO_PROVIDER` / `MODEL_NAME` from its
|
|
72
|
+
`.env`), or **sign in to a provider first** -- every daemon-level auth
|
|
73
|
+
command the daemon advertises (`anthropic-auth login`, `openrouter-auth
|
|
74
|
+
key …`, …) is a button, and any of them also runs from the prompt with no
|
|
75
|
+
session open. After a successful login the daemon sends its `auth.setup`
|
|
76
|
+
offer, which the page renders as one card: which model, whether to save
|
|
77
|
+
the provider and model to the workspace `.env`, open the session or not.
|
|
78
|
+
Accepting makes the daemon create the session itself.
|
|
79
|
+
|
|
80
|
+
A session that is already open resolved its credentials when its runner
|
|
81
|
+
booted. Storing a key afterwards (`zhipuai-auth key …`) refreshes that
|
|
82
|
+
session automatically when it runs the same provider; after editing a
|
|
83
|
+
workspace `.env` by hand, type `session reload_env` to do the same.
|
|
84
|
+
|
|
85
|
+
On a daemon with `--workspace-root`, the workspace list comes first; picking
|
|
86
|
+
a workspace goes straight to that card whether or not the workspace already
|
|
87
|
+
names a provider. The daemon's manual provider / model / API-key form is one
|
|
88
|
+
click away behind `configure` on each row, never a gate.
|
|
89
|
+
|
|
67
90
|
### Hosting the bundle yourself
|
|
68
91
|
|
|
69
92
|
`dist/` is static (assets are referenced relatively, so it can sit under any
|
|
@@ -135,10 +158,25 @@ Publishing is manual: the *Publish @jaato/web-coder-ui to npm* workflow
|
|
|
135
158
|
(`.github/workflows/publish-npm-web-coder-ui.yml`) runs the same gates as CI,
|
|
136
159
|
refuses a version already on the registry, builds, and **stages** the version
|
|
137
160
|
with the `@jaato` org's stage-only token; a maintainer with 2FA promotes it
|
|
138
|
-
(`npm stage list @jaato/web-coder-ui`, then `npm stage approve <stage-id
|
|
139
|
-
|
|
161
|
+
(`npm stage list @jaato/web-coder-ui`, then `npm stage approve <stage-id>`;
|
|
162
|
+
the 2FA step opens the browser for a passkey, or takes `--otp <code>`). It needs `@jaato/sdk` published first only at build time, from
|
|
140
163
|
the sibling checkout. Bump `version` in `package.json` first.
|
|
141
164
|
|
|
165
|
+
npm cannot stage a package it has never seen (`404` on the stage endpoint,
|
|
166
|
+
measured on this package's first run), so the **first** version was published
|
|
167
|
+
directly by a maintainer with 2FA from a checkout at the release commit:
|
|
168
|
+
|
|
169
|
+
```bash
|
|
170
|
+
cd jaato-web-coder-ui
|
|
171
|
+
npm --prefix ../jaato-sdk-ts ci && npm ci
|
|
172
|
+
npm run build # builds the SDK, type-checks, vite build
|
|
173
|
+
npm publish --access public # after `npm login`; the 2FA step opens
|
|
174
|
+
# the browser (passkey) or asks for a code
|
|
175
|
+
```
|
|
176
|
+
|
|
177
|
+
The workflow refuses by name while the package is unknown to the registry;
|
|
178
|
+
every later version stages.
|
|
179
|
+
|
|
142
180
|
Set `PLAYWRIGHT_CHROMIUM=/path/to/chrome` to use a pre-installed browser
|
|
143
181
|
instead of Playwright's download.
|
|
144
182
|
|