luxe update and /update, editable question answers, and a version bump owed once per release
- luxe update and /update update Luxe with the command for however it was installed (cargo or Homebrew), run one program at a time with the terminal attached, then check that the luxe on PATH is the new version. Luxe never downloads or replaces its own binary. The start screen says "Update available · /update". - A question's typed answer edits at its caret: arrows, word jumps, Home, End and Delete work, and up and down move through a wrapped answer before leaving it. - The version check owes a bump once per release: the version on main is the next release, and only a released one (a v-tag) has to move. - Dependency updates arrive through the sync, so Dependabot and the weekly jobs no longer run here.
This commit is contained in:
@@ -251,7 +251,8 @@ There is no telemetry. Luxe connects only to:
|
||||
2. Search providers and web pages, when the agent uses `web_search` or `web_fetch`, and GitHub
|
||||
when `web_fetch` clones a repository (`"tools": { "clone_repositories": false }` stops it)
|
||||
3. The models.dev catalog, to refresh model details (`LUXE_MODELS_DEV_REFRESH=0` stops it)
|
||||
4. The update check, once a day (`"update": { "check": false }` stops it)
|
||||
4. The update check, once a day (`"update": { "check": false }` stops it), and when you run
|
||||
`luxe update` or `/update`, which then runs your package manager's own update
|
||||
5. GitHub, through your own `gh`, when you, the agent or an [RPC client](rpc.md#github-writes) work
|
||||
with pull requests and issues. A client can write there only if you start it with
|
||||
`--github-writes`.
|
||||
|
||||
Reference in New Issue
Block a user