@howone/agent-cli 0.5.6 → 0.5.7
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/package.json
CHANGED
|
@@ -37,6 +37,19 @@ may return HTTP 404 for `/preview/wake`; report that Studio needs the matching p
|
|
|
37
37
|
|
|
38
38
|
## The loop
|
|
39
39
|
|
|
40
|
+
External coding agents install `@howone/sdk@3.0.0-beta.1` from public npm so local types and
|
|
41
|
+
definitions are available without company registry credentials. Keep the project's
|
|
42
|
+
`@howone:registry=https://registry.npmjs.org/` configuration for local installs. Cloud preview
|
|
43
|
+
and release builds use the platform-managed private registry for the same SDK version; Studio
|
|
44
|
+
also keeps its own private registry configuration. Do not copy cloud registry credentials to
|
|
45
|
+
the user's machine or change the App's SDK version merely to work around a registry error.
|
|
46
|
+
|
|
47
|
+
A local SDK download failure and a cloud dependency-install failure need different fixes.
|
|
48
|
+
For local failures, inspect the project registry and pinned version. If cloud build logs show
|
|
49
|
+
an SDK tarball being fetched from a missing npmmirror URL, report the failing dependency URL
|
|
50
|
+
and build/version ID as a platform registry or lockfile-resolution error. Repeated HowOne
|
|
51
|
+
login does not fix package downloads.
|
|
52
|
+
|
|
40
53
|
```bash
|
|
41
54
|
howone push -m "<what changed>" --json # upload changes, build on HowOne, return preview URL
|
|
42
55
|
```
|
|
@@ -73,3 +73,10 @@ sandbox functions and pass the catalog to EAX. Plain AI generation does not requ
|
|
|
73
73
|
job: that command searches the published workflow catalog and can return 404 before promotion.
|
|
74
74
|
Then run `ai sync`, inspect the manifest, and `push`.
|
|
75
75
|
4. All of this happens in the edit session's draft, like schema changes: push soon after.
|
|
76
|
+
|
|
77
|
+
If AI authoring or execution reports `Token decryption failed`, or schema validation wraps a
|
|
78
|
+
failed Studio decrypt-key callback, check `howone whoami --json` against the same API origin.
|
|
79
|
+
If account verification succeeds, preserve the App and job state and report the downstream
|
|
80
|
+
error with its request/job ID for platform diagnosis. The CLI personal token and the
|
|
81
|
+
Studio-to-EAX credential are separate; do not substitute a private npm token, ask the user to
|
|
82
|
+
paste credentials, or repeatedly log in to repair a server-to-server token failure.
|
package/templates/vite/AGENTS.md
CHANGED
|
@@ -10,6 +10,7 @@ Read this file once when entering the project, follow it during implementation,
|
|
|
10
10
|
- Common commands: `bun run dev`, `bun run typecheck`, `bun run build`
|
|
11
11
|
- The scaffold normally installs dependencies during `howone init app`. If `node_modules` is missing, run `bun install` before validation instead of treating missing binaries as code failures.
|
|
12
12
|
- `@howone/sdk@3.0.0-beta.1` uses public npm through the project's `.npmrc`; no private registry credentials are required. A package download error is separate from HowOne login.
|
|
13
|
+
- Cloud builds use the platform-managed private registry for the same SDK version. Keep local public registry configuration; do not copy cloud credentials into the project or change SDK versions to bypass a cloud download failure.
|
|
13
14
|
- Default stack: React, Vite, TypeScript, Tailwind CSS, shadcn/ui-style components, `@howone/sdk`
|
|
14
15
|
|
|
15
16
|
## Source of Truth
|