Reported: Ask Claude on an Ops Alert only types a prompt into whatever session is open. It doesn't start a session, and it doesn't say which container the alert is about (pct id) or which Proxmox node it is on right now. Most guests are HA and move between nodes.
Plan:
Proxmox guest lookup (devdesk guests): CT/VM id, name, current node, status and HA state, and IPs. Read over SSH from the nodes (DEVDESK_PVE_NODES) and cached in /var/lib/devdesk/guests.json, so stopped guests keep their last-seen IPs.
Alerts are matched to guests by the instance IP (or host name), or by name in the job/alert as a fallback marked "probably". The card shows e.g. CT 110 draupnir · monitor-02 · stopped.
Ask Claude opens a new alert-… session and starts Claude with the prompt, already sent. The server builds the prompt: rule, query, summary/description, labels, plus each target's CT id, node and ssh <node> pct exec <id> -- line, and a reminder to re-check placement with devdesk guests because of HA.
Aggregate rules with no labels (e.g. count(up == 0)) get a hint to run the inner query.
Reported: **Ask Claude** on an Ops Alert only types a prompt into whatever session is open. It doesn't start a session, and it doesn't say which container the alert is about (`pct` id) or which Proxmox node it is on right now. Most guests are HA and move between nodes.
Plan:
- [ ] Proxmox guest lookup (`devdesk guests`): CT/VM id, name, current node, status and HA state, and IPs. Read over SSH from the nodes (`DEVDESK_PVE_NODES`) and cached in `/var/lib/devdesk/guests.json`, so stopped guests keep their last-seen IPs.
- [ ] Alerts are matched to guests by the `instance` IP (or host name), or by name in the job/alert as a fallback marked "probably". The card shows e.g. `CT 110 draupnir · monitor-02 · stopped`.
- [ ] **Ask Claude** opens a new `alert-…` session and starts Claude with the prompt, already sent. The server builds the prompt: rule, query, summary/description, labels, plus each target's CT id, node and `ssh <node> pct exec <id> --` line, and a reminder to re-check placement with `devdesk guests` because of HA.
- [ ] Aggregate rules with no labels (e.g. `count(up == 0)`) get a hint to run the inner query.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reported: Ask Claude on an Ops Alert only types a prompt into whatever session is open. It doesn't start a session, and it doesn't say which container the alert is about (
pctid) or which Proxmox node it is on right now. Most guests are HA and move between nodes.Plan:
devdesk guests): CT/VM id, name, current node, status and HA state, and IPs. Read over SSH from the nodes (DEVDESK_PVE_NODES) and cached in/var/lib/devdesk/guests.json, so stopped guests keep their last-seen IPs.instanceIP (or host name), or by name in the job/alert as a fallback marked "probably". The card shows e.g.CT 110 draupnir · monitor-02 · stopped.alert-…session and starts Claude with the prompt, already sent. The server builds the prompt: rule, query, summary/description, labels, plus each target's CT id, node andssh <node> pct exec <id> --line, and a reminder to re-check placement withdevdesk guestsbecause of HA.count(up == 0)) get a hint to run the inner query.