orrevan 0.5.1 → 0.5.3
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 -0
- package/dist/orrevan.js +212 -204
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -18,6 +18,7 @@ orrevan "fix the tests" start with a first prompt
|
|
|
18
18
|
orrevan -p "question" print mode: answer once and exit (for scripts)
|
|
19
19
|
cat log.txt | orrevan -p "what went wrong?"
|
|
20
20
|
orrevan -c continue the last conversation in this folder
|
|
21
|
+
orrevan -r pick an earlier conversation in this folder
|
|
21
22
|
orrevan models list models and prices
|
|
22
23
|
orrevan balance show your credit
|
|
23
24
|
orrevan whoami account, credit, model and version
|
|
@@ -152,6 +153,8 @@ The key is stored in `~/.config/orrevan/config.json` (mode 600). Conversations a
|
|
|
152
153
|
|
|
153
154
|
### Updates
|
|
154
155
|
|
|
156
|
+
Updates are mandatory: when you start an interactive session, Orrevan checks npm (at most 3 seconds, offline starts are not delayed), installs a newer version and restarts itself with the same arguments. If the install fails (e.g. missing permissions) the current version keeps running and tells you the command to run. Print mode (`-p`) does not update itself.
|
|
157
|
+
|
|
155
158
|
`orrevan update` installs the newest version from npm (same as `npm install -g orrevan@latest`). In interactive sessions Orrevan checks npm at most once a day and shows a short notice when a newer version exists. The check sends no user data.
|
|
156
159
|
|
|
157
160
|
## Development
|