@tuned-tensor/cli 0.22.0 → 0.23.0

package/README.md

@@ -72,7 +72,7 @@ npm install -g --ignore-scripts @tuned-tensor/cli
 tt --version
 ```
 
-Uninstall with `npm uninstall -g @tuned-tensor/cli` (add
+Upgrade later with `tt upgrade`. Uninstall with `npm uninstall -g @tuned-tensor/cli` (add
 `--prefix ~/.local` if the curl installer used that prefix).
 
 Node.js 22.19.0 or newer is required. Training additionally needs
@@ -128,7 +128,7 @@ selects `tunedtensor/managed` automatically. In the shell, `/login tunedtensor`
 saves the same account token and switches the saved agent selection to
 `tunedtensor/managed`, including after restart. Managed inference requires no OpenRouter key
 or additional login. The server controls the model and request limits.
-`tt usage` shows the configured daily allowance and reported usage.
+`tt usage` shows the weekly limit remaining, the daily allowance, and reported usage.
 
 For BYO OpenRouter inference:
 
@@ -156,10 +156,19 @@ catalog providers remain available by ID. Unauthenticated entries are marked
 `auth required`. Local endpoints such as Ollama use a placeholder `apiKey` in
 `models.json` and need no TT account.
 
-Before the shell opens, `tt` performs a short, non-blocking npm version check.
-If a newer stable release is available it recommends
-`npm install -g @tuned-tensor/cli@latest`; offline or unavailable registry
-checks are ignored.
+`tt` checks npm for a newer stable release at most every 12 hours and
+remembers the answer in `~/.tuned-tensor/update-check.json`. The notice appears
+when the shell opens and after commands run in a terminal; explicit commands
+never wait on the registry. Upgrade with:
+
+```bash
+tt upgrade            # latest stable, into the same npm prefix tt runs from
+tt upgrade --check    # only report
+tt upgrade beta       # or a specific version
+```
+
+Offline or unavailable registry checks are ignored. `CI`, `TT_NO_UPDATE_CHECK=1`
+or `NO_UPDATE_NOTIFIER=1` disable the check.
 
 After a model is selected, the banner shows it and ordinary sentences go to
 the agent:
@@ -378,6 +387,37 @@ tt usage
 tt balance
 ```
 
+### Teacher-label raw data
+
+Label unlabeled inputs with a stronger teacher model, review them, and train
+an adapter on the result. Labeling uses TT credits. Add a few high-quality
+examples to the spec first: the teacher follows them as the output format.
+
+In the agent, say what you want, for example "label emails.jsonl with the
+teacher". It checks the spec and proposes the job. Approving it pushes the spec,
+uploads the file and starts labeling in the cloud. Ask for the status at any
+time. When labeling finishes, the agent asks whether to use only rows you
+reviewed or also the teacher's drafts, proposes the download, and then proposes
+the `dataset_prebuilt` edit.
+
+The same steps as commands:
+
+```bash
+tt cloud push --file tunedtensor.json                         # prints the cloud spec ID
+tt cloud label upload emails.jsonl --spec <spec-id> --watch   # {"input": "..."} per line
+tt cloud label status <job-id>
+tt cloud label rows <job-id> --status labeled
+tt cloud label accept <job-id> --rows 0,3,12                  # or --all after spot checks
+tt cloud label edit <job-id> --row 5 --output "..."
+tt cloud label download <job-id>                              # writes datasets/<job-name>/
+```
+
+`download` keeps accepted and edited rows (add `--include-unreviewed` for
+teacher drafts), drops rows blocked for secrets, removes duplicate inputs,
+drops inputs that received conflicting labels, and holds out a deterministic
+validation split (`--validation-ratio`, default 0.1). It prints the
+`dataset_prebuilt` paths to add to `tunedtensor.json`.
+
 `tt cloud specs`, `tt cloud datasets`,
 `tt cloud label`, and `tt cloud models` expose the corresponding account
 operations; each command's `--help` documents its arguments. Hosted training
@@ -392,9 +432,14 @@ original account and origin or prepare a new proposal. Cancelling older
 hosted runs remains an explicit CLI command. Without a TT token these account tools are unavailable, while
 local workflow commands and BYO inference continue to work.
 
-`tt usage` reports the server-configured daily managed inference allowance.
-Each provider completion, including a tool follow-up, consumes one request;
-failed and cancelled requests also count. Token/cost coverage shows which
+`tt usage` reports how much of the weekly managed inference limit remains,
+when it resets (Monday 00:00 UTC), and the server-configured daily request
+allowance. When the weekly limit is used up, managed requests are refused
+until the reset; BYO provider keys are unaffected. Check `tt usage` before a
+long session to avoid hitting the limit mid-task. Each provider completion, including a tool follow-up, consumes one request;
+failed and cancelled requests also count. Weekly cost includes reservations for
+running requests and estimates for interrupted requests or missing final costs.
+Token/cost coverage shows which
 requests have provider usage reports, so incomplete reporting is not mistaken
 for zero consumption. The displayed provider cost is informational, not a
 charge to TT credits. BYO provider usage is separate. `tt balance` shows TT

package/dist/{chunk-4SUXBHIY.js → chunk-RPWOCVIL.js}

@@ -7768,6 +7768,7 @@ export {
   DEFAULT_FOUNDATION_RUNS_DIR,
   DEFAULT_DECISION_RUNS_DIR,
   expandUserPath,
+  getTunedTensorHome,
   getConfigDir,
   getAgentConfigDir,
   defaultStoreRoot,
@@ -7896,4 +7897,4 @@ export {
   assessHardware,
   createRunConsoleReporter
 };
-//# sourceMappingURL=chunk-4SUXBHIY.js.map
+//# sourceMappingURL=chunk-RPWOCVIL.js.map