myte 0.0.41 → 0.0.43
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 +3 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -163,7 +163,9 @@ Feedback comments nuance:
|
|
|
163
163
|
On first coding run, it installs the branded MyteCody engine and signed
|
|
164
164
|
client assets from the Myte release manifest into a user-local Myte cache
|
|
165
165
|
after signature/hash checks. Coding execution requires those assets, a
|
|
166
|
-
reachable Myte AI Cody gateway, and `MYTEAI_API_KEY`.
|
|
166
|
+
reachable Myte AI Cody gateway, and `MYTEAI_API_KEY`. Normal coding runs use
|
|
167
|
+
the branded Codex harness with Myte context hardening; the experimental
|
|
168
|
+
controller is not the default product path.
|
|
167
169
|
- `mytecody doctor` reports both the signed MyteCody engine state and this npm
|
|
168
170
|
package version. `mytecody update` updates the engine only. Use
|
|
169
171
|
`npm install -g myte@latest` to update the launcher and the Myte API CLI
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "myte",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.43",
|
|
4
4
|
"description": "Myte developer CLI.",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"license": "MIT",
|
|
@@ -19,6 +19,6 @@
|
|
|
19
19
|
"node": ">=18"
|
|
20
20
|
},
|
|
21
21
|
"dependencies": {
|
|
22
|
-
"@mytegroupinc/myte-core": "0.0.
|
|
22
|
+
"@mytegroupinc/myte-core": "0.0.43"
|
|
23
23
|
}
|
|
24
24
|
}
|