@blinkhost/cli 2.3.0 → 2.5.0
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/CHANGELOG.md +246 -0
- package/README.md +251 -3
- package/dist/api.d.ts +1 -0
- package/dist/api.js +129 -2
- package/dist/assistant.d.ts +7 -0
- package/dist/assistant.js +460 -0
- package/dist/auth.d.ts +1 -0
- package/dist/auth.js +21 -24
- package/dist/cli.js +39 -13
- package/dist/compatibility.d.ts +1 -0
- package/dist/compatibility.js +43 -0
- package/dist/config.d.ts +2 -0
- package/dist/config.js +9 -1
- package/dist/credential-process.d.ts +19 -0
- package/dist/credential-process.js +75 -0
- package/dist/credentials.d.ts +4 -0
- package/dist/credentials.js +45 -46
- package/dist/device-flow.d.ts +24 -0
- package/dist/device-flow.js +76 -0
- package/dist/guidance.d.ts +1 -1
- package/dist/guidance.js +68 -5
- package/dist/macos-keychain-input.d.ts +6 -0
- package/dist/macos-keychain-input.js +22 -0
- package/dist/module-build.d.ts +7 -0
- package/dist/module-build.js +37 -0
- package/dist/peer-review.d.ts +8 -0
- package/dist/peer-review.js +55 -0
- package/dist/project-export.d.ts +1 -0
- package/dist/project-export.js +79 -0
- package/dist/research.d.ts +1 -0
- package/dist/research.js +42 -0
- package/dist/starter.d.ts +11 -0
- package/dist/starter.js +45 -0
- package/dist/templates.js +10 -8
- package/dist/terminal.d.ts +2 -0
- package/dist/terminal.js +12 -0
- package/dist/version.d.ts +1 -1
- package/dist/version.js +1 -1
- package/dist/windows-vault-command.d.ts +12 -0
- package/dist/windows-vault-command.js +42 -0
- package/dist/workflows.d.ts +17 -1
- package/dist/workflows.js +76 -4
- package/package.json +2 -2
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,246 @@
|
|
|
1
|
+
# BlinkHost CLI changelog
|
|
2
|
+
|
|
3
|
+
This file records customer-visible CLI changes. BlinkHost uses semantic versioning for the CLI, while security and migration impact are classified separately. A patch may therefore require prompt action, and a major release may coexist with an earlier supported line during its documented migration window.
|
|
4
|
+
|
|
5
|
+
## 2.5.0 — Idam limited preview
|
|
6
|
+
|
|
7
|
+
This release adds Idam commands for eligible accounts on an enabled control plane.
|
|
8
|
+
Idam remains a limited preview. Workspace permissions, feature availability and
|
|
9
|
+
spending limits are checked by the server. Installing the CLI does not enable
|
|
10
|
+
Idam or change a subscription. Node.js 22.12 or newer is required; no project
|
|
11
|
+
migration is needed from 2.4.0.
|
|
12
|
+
|
|
13
|
+
- Connected-review plans default to GPT-6 Luna and accept GPT-6 Luna and Sol
|
|
14
|
+
alongside GPT-5.6 Terra. Existing GPT-5.6 plan selections remain readable and
|
|
15
|
+
editable. Plan confirmation, approval and credit limits are unchanged.
|
|
16
|
+
|
|
17
|
+
- Windows sign-in allows up to 15 seconds for the read-only credential-tool
|
|
18
|
+
startup check. A timeout still stops sign-in safely; credential operations
|
|
19
|
+
retain their 30-second limit, with no automatic retry or plaintext fallback.
|
|
20
|
+
|
|
21
|
+
- Added named code review: list eligible reviewers, explicitly share
|
|
22
|
+
selected changes, inspect the shared review, approve or request changes, and
|
|
23
|
+
withdraw sharing. Decisions are bound to the reviewed version and current
|
|
24
|
+
access; they never save, build or publish. Conversations stay private.
|
|
25
|
+
Sharing is optional, but withdrawing a review does not bypass independent
|
|
26
|
+
approval required by a workspace for Idam source saves. This policy does not
|
|
27
|
+
cover starter creation, builds or deployments.
|
|
28
|
+
Reviewer options validate the server's explicit review-required flag; a missing
|
|
29
|
+
or malformed flag is not treated as permission to skip review.
|
|
30
|
+
|
|
31
|
+
- Windows sign-in no longer removes a saved credential before writing its
|
|
32
|
+
replacement. Vault failures stop the operation without retrying or displaying
|
|
33
|
+
private diagnostics; refresh credentials remain confined to an input pipe.
|
|
34
|
+
|
|
35
|
+
- macOS credential writes now send refresh tokens through a private input pipe,
|
|
36
|
+
not process arguments. A bounded single-command input rejects control
|
|
37
|
+
characters and preserves write failures; no temporary credential file or
|
|
38
|
+
automatic write retry is used.
|
|
39
|
+
|
|
40
|
+
- Added sign-in recovery guidance for globally revoked sessions and server-side
|
|
41
|
+
security updates. When a fresh sign-in is required, use the same profile and
|
|
42
|
+
explicitly request the permissions you need; an old approval link cannot
|
|
43
|
+
reconnect your device. This does not migrate project files or change billing.
|
|
44
|
+
|
|
45
|
+
- Bounded operating-system credential helpers and removed raw helper diagnostics
|
|
46
|
+
from errors. Linux keyring failures are no longer treated as missing credentials;
|
|
47
|
+
Windows missing-item handling distinguishes other vault errors. Sign-in guidance
|
|
48
|
+
explains recovery after browser approval without retrying an uncertain write.
|
|
49
|
+
Added a separate hosted-CI native-vault check for Linux, macOS and Windows
|
|
50
|
+
using only temporary synthetic credentials; ordinary local tests do not
|
|
51
|
+
modify the user's keyring. Linux and macOS checks also exercise a locked
|
|
52
|
+
synthetic keyring, bounded errors and recovery without losing saved credentials.
|
|
53
|
+
Windows checks cover normal vault operations, not a simulated desktop lock.
|
|
54
|
+
Linux also checks for retained locked credentials before reporting a missing
|
|
55
|
+
credential or successful removal when the keyring silently refuses to unlock.
|
|
56
|
+
|
|
57
|
+
- Added `projects export PROJECT_UUID --source-only --output ./source.zip` for
|
|
58
|
+
backend-only projects and unchanged source downloads. No build configuration,
|
|
59
|
+
README, schema or lockfile is generated or validated. The server must confirm
|
|
60
|
+
the requested mode. Access checks, credential screening and download limits
|
|
61
|
+
remain in effect; default portable exports are unchanged.
|
|
62
|
+
|
|
63
|
+
- Added safe, actionable source-export guidance for unsupported frontend
|
|
64
|
+
configurations, HTML package/lockfile issues and credential-screening blocks.
|
|
65
|
+
Error bodies are bounded and never printed; unknown failures retain their HTTP
|
|
66
|
+
status and request ID. Offline help explains portable and source-only exports.
|
|
67
|
+
|
|
68
|
+
- Fixed source exports returning HTTP 406 during API content negotiation.
|
|
69
|
+
Successful downloads still require a complete ZIP archive; JSON responses
|
|
70
|
+
cannot be saved as source exports.
|
|
71
|
+
|
|
72
|
+
- Fixed upload requests combining the default JSON content type with an explicit
|
|
73
|
+
multipart or binary content type, which could cause HTTP 415 errors. Custom
|
|
74
|
+
headers now replace defaults regardless of capitalization. Failed uploads are
|
|
75
|
+
still not retried automatically.
|
|
76
|
+
|
|
77
|
+
- Sign-in now explains expired codes and how to request a new one. Authorization
|
|
78
|
+
polling backs off when requested by the server and stops at expiry; uncertain
|
|
79
|
+
token-delivery or network failures are not retried automatically. Sign-in
|
|
80
|
+
addresses are validated before display or browser launch, and malformed token
|
|
81
|
+
responses cannot overwrite a saved credential.
|
|
82
|
+
|
|
83
|
+
- Corrected offline workflow help: approving a plan requires `ai:approve`,
|
|
84
|
+
separate from `ai:execute` for drafting, revising and stopping it.
|
|
85
|
+
|
|
86
|
+
- Added `projects export PROJECT_UUID --output ./project.zip` for source ZIPs,
|
|
87
|
+
distinct from Idam task exports. Existing authorization and secret screening
|
|
88
|
+
apply. Bounded downloads refuse redirects and overwrites; nothing is extracted
|
|
89
|
+
or executed. Database rows, runtime secrets and running deployments are excluded.
|
|
90
|
+
|
|
91
|
+
- Added backend starter choices, file review, explicit save approval and read-only
|
|
92
|
+
receipt recovery. Normal permissions, source revisions and module limits apply.
|
|
93
|
+
No builds, publication or AI charges; uncertain saves are never auto-retried.
|
|
94
|
+
|
|
95
|
+
- Added saved-module build choices, review, explicit approval and read-only status.
|
|
96
|
+
Normal compiler rollout, plan capacity and build metering remain authoritative;
|
|
97
|
+
no AI credits are used. Approval never publishes. CLI scope, exact digest and
|
|
98
|
+
review confirmation are required; uncertain responses are never auto-retried.
|
|
99
|
+
|
|
100
|
+
- Added explicitly confirmed `ai resume` for eligible multi-step checkpoints.
|
|
101
|
+
It preserves active work, retry delays, original spending limits and receipts;
|
|
102
|
+
it cannot restart stopped tasks or approve changes. Requires `ai:execute`.
|
|
103
|
+
Ambiguous responses are not retried automatically; inspect task status.
|
|
104
|
+
|
|
105
|
+
- Added `ai sources --project PROJECT_UUID` and bounded `research_source_ids`
|
|
106
|
+
selection for research requests. Reviewed excerpts are inspectable in task
|
|
107
|
+
details and exports, with attribution and citation status. This is not live
|
|
108
|
+
web search; sources are checked before admission and dispatch and count toward
|
|
109
|
+
the existing credit estimate. The separate source gate remains off by default.
|
|
110
|
+
|
|
111
|
+
- Extended declaration review to bounded `requirements.txt` files. Python server
|
|
112
|
+
frameworks and selected native packages receive qualified guidance, not a
|
|
113
|
+
promise of runtime support. Includes, URLs and pip options are not followed;
|
|
114
|
+
environment markers and extras are not evaluated. No code runs or changes.
|
|
115
|
+
|
|
116
|
+
- Extended the same bounded review to static `pyproject.toml` dependencies,
|
|
117
|
+
optional dependencies and build-system requirements, with separate fixed
|
|
118
|
+
labels. Dynamic/tool-specific declarations stay unknown. No build hooks run,
|
|
119
|
+
optional-group names are not disclosed, and older rule responses remain valid.
|
|
120
|
+
|
|
121
|
+
- Task exports identify the reviewed file selection separately from the full
|
|
122
|
+
proposal. An applied timestamp records a save, not a successful build or the
|
|
123
|
+
current contents of files. Review contents and approval tokens stay excluded.
|
|
124
|
+
|
|
125
|
+
- Made invisible direction and terminal controls visible in source review diffs.
|
|
126
|
+
Approval hashes still bind the original source. Structured CLI output uses
|
|
127
|
+
JSON escapes that preserve decoded values, including filenames and source.
|
|
128
|
+
|
|
129
|
+
- Added `ai compatibility --project PROJECT_UUID`: a read-only, revision-bound
|
|
130
|
+
declaration review with explicit inspection limits and no runtime certification.
|
|
131
|
+
Requires `ai:read`; no uploads, model calls, credit reservations or source edits.
|
|
132
|
+
|
|
133
|
+
- Added optional personal project guidance with `ai memory-show`, `memory-save`
|
|
134
|
+
and `memory-clear`. Saving uses an explicitly selected, bounded UTF-8 file,
|
|
135
|
+
reviewed version and project confirmation. Changes stop queued work using
|
|
136
|
+
older guidance; clearing does not erase existing task records or backups.
|
|
137
|
+
- Workload identities are refused across the personal Idam preview, so automated
|
|
138
|
+
jobs cannot inherit the creator's guidance, history or source approvals.
|
|
139
|
+
|
|
140
|
+
- Added `ai workflow-plan`, `workflow-revise`, `workflow-approve`, `workflow-status`
|
|
141
|
+
and `workflow-cancel` for bounded investigation-and-review drafts. Saving and
|
|
142
|
+
editing do not start follow-ups. Approval binds the inspected revision and
|
|
143
|
+
digest with exact workflow confirmation. `workflow-start` is a draft-only
|
|
144
|
+
compatibility alias. Saved version history remains available on each task.
|
|
145
|
+
Separately gated; plan approval does not authorize tools, tests, source writes
|
|
146
|
+
or deployments.
|
|
147
|
+
|
|
148
|
+
- Added `ai rollback-review` and `ai rollback-approve` for an explicitly reviewed,
|
|
149
|
+
source-only undo. Later file edits are protected; unchanged new files are removed
|
|
150
|
+
only when no active co-editing session references them. Original history and
|
|
151
|
+
charges remain unchanged. This is not deployment rollback or project recovery.
|
|
152
|
+
|
|
153
|
+
- `ai export` now retrieves a versioned, private task snapshot with credit totals,
|
|
154
|
+
removal status and explicit history limits. Proposed source is opt-in with
|
|
155
|
+
`--include-source`; internal context, approval tokens and input files are excluded.
|
|
156
|
+
|
|
157
|
+
- Optional, explicitly selected workspace source files for a task, with credential
|
|
158
|
+
screening and byte limits before funding. No implicit local-file upload.
|
|
159
|
+
|
|
160
|
+
- Added `ai start`, `list`, `status`, `events`, `export`, `review`, `approve` and `cancel`.
|
|
161
|
+
- Start requests use a bounded JSON file with a stable request ID and explicit budget.
|
|
162
|
+
- Source approval requires the reviewed action digest and exact task confirmation;
|
|
163
|
+
saving does not build, test, publish, purchase resources or create a Git commit.
|
|
164
|
+
- Added repeated `auth login --scope` for explicit AI permissions. Existing sessions,
|
|
165
|
+
default sign-ins and workload identities do not receive AI permissions automatically.
|
|
166
|
+
- Included offline `docs ai` with scope, privacy, retry and verification limits.
|
|
167
|
+
|
|
168
|
+
These commands require the matching control-plane integration and current project
|
|
169
|
+
access. They were not included in 2.4.0. No automatic update is performed.
|
|
170
|
+
|
|
171
|
+
## 2.4.0 — 2026-09-02
|
|
172
|
+
|
|
173
|
+
### Added
|
|
174
|
+
|
|
175
|
+
- Terminal-accessible release notes from BlinkHost's immutable public release registry.
|
|
176
|
+
- Cached, non-blocking update notices with package-manager-specific instructions.
|
|
177
|
+
- Dashboard-linked compatibility guidance for confirmed CLI and SDK versions.
|
|
178
|
+
|
|
179
|
+
### Changed
|
|
180
|
+
|
|
181
|
+
- Token refresh reports the installed CLI version so upgrading does not leave stale session evidence.
|
|
182
|
+
- Routine notices remain in the CLI and dashboard; required, security and retirement impact use targeted operational communication.
|
|
183
|
+
|
|
184
|
+
### Compatibility
|
|
185
|
+
|
|
186
|
+
- Node.js 22.12 or newer.
|
|
187
|
+
- No project migration is required from 2.3.0.
|
|
188
|
+
|
|
189
|
+
## 2.3.0 — 2026-08-31
|
|
190
|
+
|
|
191
|
+
### Added
|
|
192
|
+
|
|
193
|
+
- Project-scoped `functions status` capability discovery.
|
|
194
|
+
- Direct trigger, invocation, result, cancellation and retry workflows.
|
|
195
|
+
|
|
196
|
+
### Security and reliability
|
|
197
|
+
|
|
198
|
+
- Function payloads are bounded JSON objects.
|
|
199
|
+
- Retries support explicit idempotency keys.
|
|
200
|
+
- Update checks never install software and do not block CI or structured output.
|
|
201
|
+
|
|
202
|
+
### Compatibility
|
|
203
|
+
|
|
204
|
+
- Node.js 22.12 or newer.
|
|
205
|
+
- Backend SDK contract 1.1.0.
|
|
206
|
+
- No migration is required from 2.2.0.
|
|
207
|
+
|
|
208
|
+
## 2.2.0 — 2026-08-30
|
|
209
|
+
|
|
210
|
+
### Added
|
|
211
|
+
|
|
212
|
+
- JavaScript, TypeScript and Python Function workflows with explicit beta availability.
|
|
213
|
+
- Commands for background, event and scheduled triggers.
|
|
214
|
+
|
|
215
|
+
### Changed
|
|
216
|
+
|
|
217
|
+
- Function availability became project- and rollout-aware rather than inferred from the installed CLI version.
|
|
218
|
+
|
|
219
|
+
## 2.1.0 — 2026-08-29
|
|
220
|
+
|
|
221
|
+
### Added
|
|
222
|
+
|
|
223
|
+
- Public npm installation for `@blinkhost/cli`.
|
|
224
|
+
- Existing-repository detection, local validation, development and build checks.
|
|
225
|
+
- Device authorization, named profiles and revocable CLI sessions.
|
|
226
|
+
- Workload identity support for secretless GitHub automation.
|
|
227
|
+
|
|
228
|
+
### Security
|
|
229
|
+
|
|
230
|
+
- Refresh credentials are stored in the operating-system credential service.
|
|
231
|
+
- Secret values are accepted through standard input rather than command arguments.
|
|
232
|
+
|
|
233
|
+
## 2.0.0 — 2026-08-29
|
|
234
|
+
|
|
235
|
+
### Added
|
|
236
|
+
|
|
237
|
+
- Stable command groups for projects, source connections, previews, builds, deployments, backend modules, databases and organizations.
|
|
238
|
+
- Machine-readable JSON output and stable exit categories.
|
|
239
|
+
- Explicit confirmation for destructive operations.
|
|
240
|
+
|
|
241
|
+
## Compatibility and support policy
|
|
242
|
+
|
|
243
|
+
- BlinkHost documents supported Node.js, manifest, runtime, ABI and SDK versions with each release.
|
|
244
|
+
- Deprecations include an alternative and a published deadline before removal unless an active security issue requires faster action.
|
|
245
|
+
- Required and security migrations identify affected versions and link to a tested guide.
|
|
246
|
+
- Run `blinkhost update check` for the current version comparison or `blinkhost update notes [VERSION]` for release detail.
|
package/README.md
CHANGED
|
@@ -7,14 +7,202 @@ The BlinkHost CLI brings project setup, local development, source control, previ
|
|
|
7
7
|
Node.js 22.12 or newer is required.
|
|
8
8
|
|
|
9
9
|
```bash
|
|
10
|
-
npm install --global @blinkhost/cli@2.
|
|
10
|
+
npm install --global @blinkhost/cli@2.5.0
|
|
11
11
|
blinkhost --version
|
|
12
12
|
```
|
|
13
13
|
|
|
14
14
|
Signed release archives, checksums, the CycloneDX SBOM, and Sigstore verification bundle are available at <https://github.com/blinkhost-ltd/blinkhost-cli/releases>.
|
|
15
15
|
|
|
16
|
+
## Current release
|
|
17
|
+
|
|
18
|
+
### 2.5.0 — Idam limited preview
|
|
19
|
+
|
|
20
|
+
- Added Idam task, source-review, starter, build, export and connected-review commands.
|
|
21
|
+
- Connected-review plans default to GPT-6 Luna and support GPT-6 Sol and GPT-5.6 Terra; older GPT-5.6 plans remain readable.
|
|
22
|
+
- Improved scoped sign-in and operating-system credential handling on Linux, macOS and Windows.
|
|
23
|
+
|
|
24
|
+
Idam remains a limited preview. Access depends on the server rollout, current
|
|
25
|
+
project permissions and available credits. Installing this CLI does not enable
|
|
26
|
+
Idam or change a subscription. No project migration is required from 2.4.0.
|
|
27
|
+
|
|
28
|
+
Run `blinkhost update notes` to read published notes in the terminal. The complete version history and compatibility policy are maintained in [CHANGELOG.md](./CHANGELOG.md) and the [developer release notes](https://app.blinkhost.me/docs/releases).
|
|
29
|
+
|
|
16
30
|
## Start safely
|
|
17
31
|
|
|
32
|
+
### Idam limited preview
|
|
33
|
+
|
|
34
|
+
Request a review of selected code with
|
|
35
|
+
`ai peer-options TASK_UUID --project PROJECT_UUID`, then
|
|
36
|
+
`ai peer-invite TASK_UUID --project PROJECT_UUID --reviewer USER_ID --digest ACTION_DIGEST --confirm TASK_UUID`.
|
|
37
|
+
Prepare and inspect `ai review` first. Only the selected before-and-after code
|
|
38
|
+
is shared with the named owner or administrator; conversations and other
|
|
39
|
+
proposed files remain private. The reviewer uses `ai peer-inbox --project PROJECT_UUID`,
|
|
40
|
+
`ai peer-review PEER_UUID --project PROJECT_UUID`, then
|
|
41
|
+
`ai peer-approve PEER_UUID --project PROJECT_UUID --digest REVIEW_DIGEST --confirm PEER_UUID`
|
|
42
|
+
or `peer-decline` with the same options. Read commands need `ai:read`; sharing
|
|
43
|
+
and decisions need `ai:approve`. Decisions never save, build or publish.
|
|
44
|
+
The requester saves separately after approval, or explicitly withdraws with
|
|
45
|
+
`ai peer-withdraw TASK_UUID --project PROJECT_UUID --peer PEER_UUID --confirm TASK_UUID`.
|
|
46
|
+
Sharing is optional, but your workspace may require independent approval before
|
|
47
|
+
Idam source saves. Withdrawal ends sharing and preserves history; it does not
|
|
48
|
+
bypass workspace-required review.
|
|
49
|
+
Reviews expire after at most 15 minutes and changes to source or permissions
|
|
50
|
+
require fresh review. Inspect current status after a timeout; do not retry
|
|
51
|
+
automatically. This policy covers Idam source saves only, not starter creation,
|
|
52
|
+
builds or deployments; those retain their separate permissions and approvals.
|
|
53
|
+
These commands require current Idam access. See `blinkhost docs ai`.
|
|
54
|
+
|
|
55
|
+
Create a supported backend starter with `ai starters --project PROJECT_UUID` and
|
|
56
|
+
`ai starter-review --project PROJECT_UUID --name api --language LANGUAGE_ID --revision SOURCE_REVISION --request-id REQUEST_UUID`.
|
|
57
|
+
Inspect the returned files and retain the review UUID before approving with
|
|
58
|
+
`ai starter-approve REVIEW_UUID --project PROJECT_UUID --digest ACTION_DIGEST --confirm REVIEW_UUID`.
|
|
59
|
+
This saves new source through normal module limits; it does not build or publish.
|
|
60
|
+
No AI credits are used. After an uncertain response, use
|
|
61
|
+
`ai starter-status REVIEW_UUID --project PROJECT_UUID` to reconcile the original
|
|
62
|
+
save, never another create. Read, preparation and approval require `ai:read`,
|
|
63
|
+
`ai:execute` and `ai:approve` respectively.
|
|
64
|
+
|
|
65
|
+
Saved WASM modules can be reviewed for a normal, metered build using
|
|
66
|
+
`ai build-modules --project PROJECT_UUID`, followed by
|
|
67
|
+
`ai build-review --project PROJECT_UUID --module MODULE_UUID --revision SOURCE_REVISION --request-id REQUEST_UUID`.
|
|
68
|
+
Retain the request UUID. Review the source in the IDE and the returned digest,
|
|
69
|
+
usage policy and expiry. Then explicitly approve with
|
|
70
|
+
`ai build-approve REVIEW_UUID --project PROJECT_UUID --digest ACTION_DIGEST --confirm REVIEW_UUID`.
|
|
71
|
+
Read/list needs `ai:read`, preparation needs `ai:execute`, and approval needs
|
|
72
|
+
`ai:approve`. This uses normal build allowance, configured overages and duration
|
|
73
|
+
usage—not AI credits. It does not publish, promote an artifact or commit files.
|
|
74
|
+
Unsaved edits are excluded. After a timeout, use
|
|
75
|
+
`ai build-status REVIEW_UUID --project PROJECT_UUID` before any further action;
|
|
76
|
+
do not create a new review to repeat an uncertain build. See `blinkhost docs ai`.
|
|
77
|
+
These commands require current Idam access and an available module compiler.
|
|
78
|
+
|
|
79
|
+
For an eligible multi-step task, use
|
|
80
|
+
`blinkhost ai resume TASK_UUID --confirm TASK_UUID` with `ai:execute` to request
|
|
81
|
+
continuation from its saved checkpoint. This keeps the same task, original
|
|
82
|
+
credit limit and confirmed usage. Active work and retry delays are preserved;
|
|
83
|
+
it does not restart stopped or completed tasks, increase spending, approve
|
|
84
|
+
changes or repeat confirmed execution. Project access, revision and guidance
|
|
85
|
+
are checked again. After a timeout, inspect `ai status` before taking another
|
|
86
|
+
action.
|
|
87
|
+
|
|
88
|
+
Reviewed public sources have a separate feature gate that is off by default. Use
|
|
89
|
+
`blinkhost ai sources --project PROJECT_UUID` with `ai:read` to inspect the
|
|
90
|
+
available excerpts, attribution and capture/review dates. To use them, set
|
|
91
|
+
`"mode": "research"` and `"research_source_ids": ["SOURCE_SHA256"]` in the
|
|
92
|
+
request JSON (up to four unique IDs). This does not browse or fetch websites.
|
|
93
|
+
Source text counts toward the credit estimate. Expired or withdrawn sources
|
|
94
|
+
cannot start new work; already dispatched work can finish. Task status/export
|
|
95
|
+
retains the excerpts provided, not later versions of the source website. A model
|
|
96
|
+
citation is not proof that a conclusion is correct.
|
|
97
|
+
|
|
98
|
+
Source-review diffs use `[U+…]` markers for invisible control characters and
|
|
99
|
+
annotations for line endings. They are review displays, not patches to copy.
|
|
100
|
+
Approvals bind the original source, which these annotations do not modify.
|
|
101
|
+
Structured terminal output escapes controls while preserving the exact decoded
|
|
102
|
+
JSON values. Ordinary Unicode is retained; this is not a confusable-character
|
|
103
|
+
detector or a guarantee that proposed code is safe.
|
|
104
|
+
|
|
105
|
+
Version 2.5.0 includes `blinkhost ai` task and reviewed-change commands, with
|
|
106
|
+
offline help at `blinkhost docs ai`. They require an enabled Idam preview.
|
|
107
|
+
AI task execution (`ai:execute`) and source
|
|
108
|
+
approval (`ai:approve`) are separate, explicitly requested permissions; existing
|
|
109
|
+
sessions do not gain these permissions automatically. See the [changelog](./CHANGELOG.md).
|
|
110
|
+
|
|
111
|
+
Saving an approved proposal changes workspace source only. Build, test and preview
|
|
112
|
+
before publishing. To share source with Azure OpenAI for a task, include optional
|
|
113
|
+
`source_paths` in its request JSON (up to eight project-relative paths of saved
|
|
114
|
+
workspace files, 16 KiB each / 24 KiB total). No local files are uploaded. Review
|
|
115
|
+
selected files for credentials; automated screening is not exhaustive. Omit the
|
|
116
|
+
field to share structural metadata only.
|
|
117
|
+
|
|
118
|
+
Unknown model usage is never automatically retried or refunded.
|
|
119
|
+
|
|
120
|
+
To review only part of a proposal, use `blinkhost ai review TASK_UUID --path
|
|
121
|
+
src/example.ts` (repeat `--path` for more files). With no paths, all proposed files
|
|
122
|
+
are included. Inspect every returned diff before approval. Changing the selection
|
|
123
|
+
requires a fresh review; saving finishes the task and omitted files may still be
|
|
124
|
+
needed for the application to work. Task exports distinguish the full proposal
|
|
125
|
+
from `review.paths`; only a populated review `applied_at` records that selection's
|
|
126
|
+
save. This is file selection, not automatic dependency analysis or project copying.
|
|
127
|
+
|
|
128
|
+
Use `blinkhost ai compatibility --project PROJECT_UUID` for a read-only review of
|
|
129
|
+
the saved project's declared dependencies. It requires `ai:read` and the enabled
|
|
130
|
+
Idam preview. Results identify the workspace
|
|
131
|
+
revision, manifest paths, declaration sections and inspection limits. Only a fixed
|
|
132
|
+
set of npm and Python package names is checked in `package.json` and single-line
|
|
133
|
+
`requirements.txt` and static `pyproject.toml` declarations. Runtime, optional and
|
|
134
|
+
build-system requirements keep distinct labels; build-only use is not runtime
|
|
135
|
+
use. Python markers and extras are not evaluated. Dynamic dependencies, tool
|
|
136
|
+
overrides, includes, pip options, URLs and other manifest formats need manual
|
|
137
|
+
review. No lockfile or transitive dependency graph is resolved.
|
|
138
|
+
No findings is **not a compatibility pass**. This command uploads no local
|
|
139
|
+
files, makes no model calls, reserves no credits and does not install, build, test,
|
|
140
|
+
adapt or deploy code. Customer backend execution remains WASM-only. Review project
|
|
141
|
+
metadata before sharing command output, and rerun after workspace changes.
|
|
142
|
+
|
|
143
|
+
You can save optional project guidance for your own future tasks using the
|
|
144
|
+
`ai memory-show`, `memory-save` and `memory-clear` commands. First run
|
|
145
|
+
`blinkhost ai memory-show --project PROJECT_UUID` and inspect the saved version.
|
|
146
|
+
Then use `blinkhost ai memory-save --project PROJECT_UUID --file @guidance.txt
|
|
147
|
+
--expected-version VERSION --confirm PROJECT_UUID` to upload a regular UTF-8 file
|
|
148
|
+
of at most 4 KiB. Saving authorizes sending this guidance with future model tasks;
|
|
149
|
+
it does not change permissions, runtime support or billing. Keep credentials out.
|
|
150
|
+
`memory-show` prints private text: take care with logs and shared terminals.
|
|
151
|
+
|
|
152
|
+
To clear it, run `blinkhost ai memory-clear --project PROJECT_UUID
|
|
153
|
+
--expected-version VERSION --confirm PROJECT_UUID`. Editing or clearing prevents
|
|
154
|
+
queued tasks and later workflow steps from using an older version. Work already
|
|
155
|
+
sent may finish. Existing task copies and backups are not erased. After a timeout
|
|
156
|
+
or conflict, reload and compare with `memory-show` before another write; the CLI
|
|
157
|
+
never retries it automatically. Reading requires `ai:read`; saving and clearing
|
|
158
|
+
require `ai:execute`. CI workload identities cannot use the personal Idam preview,
|
|
159
|
+
including indirectly through task creation or history, regardless of token scopes.
|
|
160
|
+
|
|
161
|
+
Connected investigation-and-review sequences require a separate feature gate.
|
|
162
|
+
Inspect `ai status TASK_UUID` first. Then
|
|
163
|
+
`ai workflow-plan TASK_UUID --maximum-units TOTAL_LIMIT --confirm TASK_UUID`
|
|
164
|
+
saves a draft with two follow-ups of 80 credits each. `TOTAL_LIMIT` must
|
|
165
|
+
cover the original task's approved limit plus 160 credits, up to 2,000 total.
|
|
166
|
+
Saving does not approve follow-ups; the original task continues independently.
|
|
167
|
+
`workflow-start` remains a draft-only compatibility alias. Use
|
|
168
|
+
`ai workflow-status WORKFLOW_UUID` to inspect the saved plan and version history.
|
|
169
|
+
To change a draft, use `ai workflow-revise WORKFLOW_UUID --request @plan.json
|
|
170
|
+
--expected-revision VERSION --digest PLAN_DIGEST --confirm WORKFLOW_UUID`.
|
|
171
|
+
The regular UTF-8 JSON file (16 KiB maximum) contains exactly `steps`,
|
|
172
|
+
`maximum_units` and `maximum_context_units`; see `blinkhost docs ai` for the schema.
|
|
173
|
+
Then approve the version you inspected with `ai workflow-approve WORKFLOW_UUID
|
|
174
|
+
--expected-revision VERSION --digest PLAN_DIGEST --confirm WORKFLOW_UUID`.
|
|
175
|
+
Changed drafts require fresh review; approved or stopped plans cannot be edited.
|
|
176
|
+
Reading requires `ai:read`, preparing or revising a plan requires `ai:execute`,
|
|
177
|
+
and approving it requires the separate `ai:approve` permission. Approval permission
|
|
178
|
+
does not grant access to another user's plan or bypass current project access.
|
|
179
|
+
These operations grant no funding and reserve no additional credits. Each later
|
|
180
|
+
step checks available balance and current project access. Use
|
|
181
|
+
`ai workflow-cancel WORKFLOW_UUID --confirm WORKFLOW_UUID` to stop later steps.
|
|
182
|
+
After a timeout, task status exposes `analysis_workflow.id`; inspect it before
|
|
183
|
+
making another write. Never automatically retry approval or reuse stale versions.
|
|
184
|
+
These are drafts, not executed tests or deployments.
|
|
185
|
+
Follow-ups retain the original request and previous draft under their own task
|
|
186
|
+
retention periods. Removing one task does not remove copies in another.
|
|
187
|
+
|
|
188
|
+
`blinkhost ai export TASK_UUID --json` prints a versioned private task record.
|
|
189
|
+
Add `--include-source` only when you want proposed source-file copies included.
|
|
190
|
+
Requests and narrative may still contain private information: review before
|
|
191
|
+
sharing. This is not a project backup or deployment certificate. Removed content
|
|
192
|
+
is not reconstructed; long histories are marked partial, and existing downloads
|
|
193
|
+
are outside task-history retention. See `blinkhost docs ai` for limits.
|
|
194
|
+
|
|
195
|
+
To undo an Idam source save in the limited preview, run
|
|
196
|
+
`blinkhost ai rollback-review TASK_UUID --json`, inspect its file restorations and
|
|
197
|
+
removals, then run `blinkhost ai rollback-approve TASK_UUID --digest UNDO_ACTION_DIGEST --confirm TASK_UUID`.
|
|
198
|
+
This is a separate, expiring approval, not the original source-save digest.
|
|
199
|
+
Preparing requires `ai:execute`; confirming requires `ai:approve`. Later edits to
|
|
200
|
+
affected files block undo. Other files and folders are preserved. Removed task
|
|
201
|
+
content cannot be recovered. Undo does not reverse deployments, charges or Git
|
|
202
|
+
commits. Check the task after a timeout; these commands do not automatically retry.
|
|
203
|
+
|
|
204
|
+
### Local readiness
|
|
205
|
+
|
|
18
206
|
```bash
|
|
19
207
|
blinkhost quickstart
|
|
20
208
|
blinkhost docs
|
|
@@ -41,8 +229,28 @@ blinkhost profile use work
|
|
|
41
229
|
|
|
42
230
|
Revoke a device with `blinkhost auth revoke SESSION_ID` or disconnect all CLI sessions for the active profile with `blinkhost auth logout`.
|
|
43
231
|
|
|
232
|
+
If your CLI session is rejected after signing out of all devices, an account
|
|
233
|
+
security change or a BlinkHost security update, run `blinkhost auth login` again
|
|
234
|
+
with the same `--profile` and any explicit `--scope` options you need. Sign in to
|
|
235
|
+
the correct account in your browser and review the new request before approving.
|
|
236
|
+
Reopening an old approval link does not reconnect the CLI. Reauthentication does
|
|
237
|
+
not change your project files, deployments or billing plan. If the new sign-in is
|
|
238
|
+
blocked, check email verification and any required legal acceptance in the
|
|
239
|
+
dashboard; do not copy credentials from another device to work around it.
|
|
240
|
+
|
|
44
241
|
Interactive credential storage uses macOS Keychain, Windows Password Vault, or Linux Secret Service (`secret-tool` with an available, unlocked session keyring). The CLI intentionally does not fall back to a plaintext refresh-token file. Headless systems should use a registered GitHub OIDC workload or a short-lived runtime access token.
|
|
45
242
|
|
|
243
|
+
Before opening browser authorization, the CLI checks that the credential tooling can run. This does not prove that your keyring is unlocked; on Linux, start an unlocked Secret Service session first. Missing tooling is reported before a device authorization is requested.
|
|
244
|
+
|
|
245
|
+
Credential-tool checks stop after five seconds on macOS and Linux, or 15 seconds
|
|
246
|
+
on Windows to allow PowerShell to start. Credential reads and writes stop after
|
|
247
|
+
30 seconds. These checks do not retry. Keyring errors use safe messages without displaying helper
|
|
248
|
+
output. On Linux, an unavailable session keyring is reported as a credential-service
|
|
249
|
+
failure rather than a missing sign-in. Unlock or restart your Secret Service session.
|
|
250
|
+
If browser approval succeeded but saving the session failed or timed out, review
|
|
251
|
+
your CLI sessions in BlinkHost settings before starting another sign-in. The CLI
|
|
252
|
+
does not automatically retry credential writes or fall back to plaintext storage.
|
|
253
|
+
|
|
46
254
|
## Create or adopt a project
|
|
47
255
|
|
|
48
256
|
```bash
|
|
@@ -74,6 +282,44 @@ blinkhost test .
|
|
|
74
282
|
|
|
75
283
|
## Remote workflows
|
|
76
284
|
|
|
285
|
+
### Download project source
|
|
286
|
+
|
|
287
|
+
```bash
|
|
288
|
+
blinkhost projects export PROJECT_UUID --output ./project-source.zip --json
|
|
289
|
+
```
|
|
290
|
+
|
|
291
|
+
This downloads source and portable configuration through BlinkHost's existing
|
|
292
|
+
export service. It requires `projects:read` and an owner, admin or developer role;
|
|
293
|
+
connecting GitHub is optional. Choose a new `.zip` filename in an existing
|
|
294
|
+
directory without symbolic links. Downloads are limited to 32 MiB and 30 seconds.
|
|
295
|
+
The CLI does not follow redirects, replace existing files, extract the ZIP or run
|
|
296
|
+
its contents. It returns a SHA-256 checksum and saves with private permissions
|
|
297
|
+
where POSIX permissions apply.
|
|
298
|
+
|
|
299
|
+
The default portable export requires a supported frontend configuration. For
|
|
300
|
+
backend-only projects, or to download source without generating build files, use:
|
|
301
|
+
|
|
302
|
+
```bash
|
|
303
|
+
blinkhost projects export PROJECT_UUID --source-only --output ./source.zip --json
|
|
304
|
+
```
|
|
305
|
+
|
|
306
|
+
Source-only mode preserves workspace files and validated project assets, including
|
|
307
|
+
any existing configuration. It does not generate or validate build configuration,
|
|
308
|
+
README files, database schemas or lockfiles. A connected repository's saved base
|
|
309
|
+
is overlaid with the workspace; files outside the application root are preserved.
|
|
310
|
+
It is not a fresh fetch of the remote branch. The server must explicitly confirm
|
|
311
|
+
source-only mode, so an older server cannot silently return generated files.
|
|
312
|
+
The same authorization, credential screening and size limits apply in both modes.
|
|
313
|
+
Known configuration and credential-screening errors include next steps and a
|
|
314
|
+
request ID; raw server details are not printed. Export never repairs your stored
|
|
315
|
+
configuration, installs dependencies or changes source on your behalf.
|
|
316
|
+
|
|
317
|
+
The archive is **not a database backup or a running deployment**. Database rows,
|
|
318
|
+
runtime secrets, deployed artifacts and complete Git history are not included.
|
|
319
|
+
Source is screened for possible credentials, but review it before sharing.
|
|
320
|
+
Configure resources and secrets separately, and check compatibility before running
|
|
321
|
+
the exported application elsewhere. `ai export` instead exports a task record.
|
|
322
|
+
|
|
77
323
|
Resource commands use the same pattern:
|
|
78
324
|
|
|
79
325
|
```bash
|
|
@@ -166,19 +412,21 @@ Stable exit codes distinguish usage, validation, filesystem, authentication, net
|
|
|
166
412
|
```bash
|
|
167
413
|
blinkhost completion bash # also zsh, fish, or powershell
|
|
168
414
|
blinkhost update check
|
|
415
|
+
blinkhost update notes
|
|
416
|
+
blinkhost update notes 2.4.0
|
|
169
417
|
blinkhost plugins add /absolute/path/to/plugin --name example
|
|
170
418
|
blinkhost plugins verify example
|
|
171
419
|
blinkhost plugins run example -- arguments
|
|
172
420
|
```
|
|
173
421
|
|
|
174
|
-
Update checks never install software. Plugins require explicit local approval, are pinned to their executable SHA-256 digest, stop when the executable changes, and receive neither BlinkHost credentials nor the parent environment. A plugin is still third-party code running with your operating-system account; review it before adding it.
|
|
422
|
+
Update checks never install software. At most once every 48 hours, an interactive terminal may perform a cached, time-bounded check after a successful command and print one upgrade line. Checks are suppressed in CI, JSON output, and non-interactive sessions; set `BLINKHOST_NO_UPDATE_NOTIFIER=1` to suppress them explicitly. Plugins require explicit local approval, are pinned to their executable SHA-256 digest, stop when the executable changes, and receive neither BlinkHost credentials nor the parent environment. A plugin is still third-party code running with your operating-system account; review it before adding it.
|
|
175
423
|
|
|
176
424
|
Pin or roll back explicitly with `npm install --global @blinkhost/cli@VERSION`. Tagged packages are published from the `blinkhost-ltd/blinkhost-cli` release workflow through npm Trusted Publishing with provenance. To verify a downloaded GitHub release, first run `sha256sum --check SHA256SUMS`, then verify its Sigstore bundle:
|
|
177
425
|
|
|
178
426
|
```bash
|
|
179
427
|
cosign verify-blob \
|
|
180
428
|
--bundle SHA256SUMS.sigstore.json \
|
|
181
|
-
--certificate-identity "https://github.com/blinkhost-ltd/blinkhost-cli/.github/workflows/release.yml@refs/tags/v2.
|
|
429
|
+
--certificate-identity "https://github.com/blinkhost-ltd/blinkhost-cli/.github/workflows/release.yml@refs/tags/v2.5.0" \
|
|
182
430
|
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
|
|
183
431
|
SHA256SUMS
|
|
184
432
|
```
|
package/dist/api.d.ts
CHANGED
|
@@ -11,6 +11,7 @@ export declare class ApiClient {
|
|
|
11
11
|
private constructor();
|
|
12
12
|
static create(profileName?: string): Promise<ApiClient>;
|
|
13
13
|
static fromAccessToken(profileName: string, profile: Profile, accessToken: string): ApiClient;
|
|
14
|
+
projectArchive(projectId: string, mode?: 'portable' | 'source'): Promise<Buffer>;
|
|
14
15
|
request(path: string, init?: RequestInit): Promise<unknown>;
|
|
15
16
|
rememberIdentity(identity: {
|
|
16
17
|
id?: number;
|