User guideWayseer 0.28.3Contents

Actions

Wayseer reads by default. A module may also offer actions on its entities, such as restarting a deployment or silencing an alert, but none runs unless your config allows it for that module instance:

modules:
  - kind: kubernetes
    name: prod
    actions: [restart, scale]

Each module's page lists the actions it offers: Kubernetes restarts and scales deployments and deletes pods, Prometheus silences alerts in Alertmanager, and Proxmox VE starts, shuts down and reboots guests.

An action you have not listed is never offered, and every action waits for you to confirm it. An external module offers only the actions its signed manifest declares, as well. The language model can propose an action; only you can run it (how). So can a program on the control socket.

Offering and confirming

Focus an entity and press a to list the actions allowed on it. Up and Down move and Enter picks one. Detail names them under the entity's kind, as Actions: restart, scale (a). With none allowed, a says so in the status bar.

In the palette, an action's ID and an entity's name make a line of their own: restart payments-api, or scale payments-api replicas=3 with its parameters. >action.run does the same with action=, ref= and params=.

Either way the confirm panel opens. It says what runs, on what, through which module instance, what changes, and the parameters. Up and Down move among the parameters, and Left and Right step one: a number within its bounds, a duration from a list, or one of its choices. A number can also be typed. Y runs it, and N or Esc declines it. Enter does nothing there, so a habit cannot confirm an action. A parameter with no default must be set first, and one out of bounds is refused in the panel.

While an action runs, the status bar says Running restart on payments-api…. Its outcome then replaces that line until your next key, in the color of a healthy entity, or of a failing one with the module's error. One action runs at a time; a says which is running meanwhile.

The action log

Every action proposed is kept, whether you ran it or declined it, in actions.jsonl, on Linux usually ~/.local/state/wayseer/actions.jsonl (where files are kept), readable only by you. Each line has the time, the action and its parameters, the entity, the module instance, who proposed it (owner, model, or control for a control client) and how it ended: declined, ok, or failed with the module's error. Anything in an error shaped like a password or token is replaced with [redacted]. The newest 10,000 actions are kept.

>actions.log shows the last 20, newest first.

Each outcome is also an event on the entity, of kind action, from Wayseer itself: the Timeline marks it, Stream lists it, and a failed action is a warning that What changed reports.