5 ms·

Nanobot will happily ssh to a host and do things on it. I'm sure that's just a skill away for pi or opencode.

embedding-shape 5mo ago
Most if not every agent has access to bash or similar, which ssh typically is available. You don't need any bloated skills or anything, as long as you include `host is available via user@10.55` or whatever, and you have authentication properly setup, it'll figure it out.
ytjohn 5mo ago
Confirming that Pi can definitely handles this. I've written a harness "factotum" based on pi just for managing my homelab and my radio club's systems. Has absolutely no issue sshing into things remotely, running ansible/helm/kubectl/talosctl commands. There's a few skills, a and an extension to switch inventory. The extension is only needed because I want to switch between the two organizations. It's pretty slick. One of my use cases was just getting my homelab under control. So one of the first tasks I gave it was to go find everything that's running on these hosts, system services, docker compose, kube pods, etc. Builds an inventory, memory, todos. Switches the script from "ai helps me launch more experiments to lose track of" to "organized and back under config management". .pi/factotum/ ├── active-profile ├── profiles │ ├── club │ │ ├── config.yaml │ │ ├── inventory │ │ │ └── hosts.yaml │ │ └── todos │ │ ├── 22a094a3.md │ │ ├── 427ad844.md │ │ ├── 4c185be7.md │ │ ├── 4d0eea0f.md │ │ └── bcf069a4.md │ ├── examples │ │ ├── config.yaml │ │ └── inventory │ │ └── hosts.yaml │ └── local │ ├── config.yaml │ ├── inventory │ │ └── hosts.yaml │ ├── memories │ │ ├── axel-services.md │ │ ├── fran-mydiffuser.md │ │ ├── fran-services.md │ │ ├── ruffclus-cluster.md │ │ └── ruffclus-paperless-ngx.md │ └── todos │ ├── 0f7fd63e.md │ ├── 75c82ceb.md │ ├── 9cb63594.md │ ├── af33e08f.md │ ├── ba490542.md │ ├── c09c144f.md │ ├── c5f7f8a8.md │ └── d4c4b287.md ├── schemas │ ├── PROJECT_ARCHITECTURE.md │ └── project-architecture.yaml ├── task-templates │ └── host-audit.yaml └── tools └── host_audit_runner.sh
- iib 5mo ago
  How do you use `pi` to ssh? I use `oh-my-pi`, and tried the `/ssh` command, but I couldn't get it to work. Then I saw a suggestion somewhere to just run `!ssh` to place things into the agent's context. Is there a way to use it like "The current directory is at `ssh server`" and have the agent work from there?
cyanydeez 5mo ago
so, to be clear, is it just doing random bash commands to runn ssh or is it a actual tool, eg, node-ssh command interface. i would not trust bash execution of SSH because it can easily hallucinate local commands instead of remote.
- hrimfaxi 5mo ago
  > i would not trust bash execution of SSH because it can easily hallucinate local commands instead of remote. Why would it be more likely to hallucinate local commands instead of remote commands if it is in an active SSH session?
  - cyanydeez 5mo ago
    I think you're reading into the statement. It can equally hallucinate commands. Fine. The problem is, if I'm working on a remote machine, I'm generally doing things that I'd be less concerned about. If I'm on a VPN and it rm -rf / while I'm trying to clean it up; bad break, but it's not _my machine_ it just removed root on. So if your LLM is just running something like `ssh <remote> "<cmd>"` it could easily foget the ssh <remote> part and suddenly you're modifying your local system. So it's one thing to YOLO on production servers, etc, but wiping out something locally is a significantly different event. Imagine it erasing all your scripts or whatever. Anyway, the point is: I wouldn't trust an agent operating with just a bash cli running ssh commands.
- JeremyNT 5mo ago
  Background: I use OpenCode to do this. Just tell it to use ssh from the shell. From there you can give it extra context to describe the target (if you know/care about it), or just let it loose and if the environment doesn't have what it expects it will "figure something out" - just the same as with your local env. If there's some least common denominator you know about e.g. python it can streamline things if you tell it to just use that for everything.
  - cyanydeez 5mo ago
    I don't think you understand. I'm well aware it can run whatever command on bash. You're taking a significant risk asking it to do what it's doing via ssh, because it could easily forget that it's suppose to be doing ssh and do whatever locally. The point is: opencode should have a specific deterministic tool like https://www.npmjs.com/package/node-ssh https://www.npmjs.com/package/node-ssh where commands can only be run; the environment can only be the remote; etc. The last thing I would want is for it to suddenly forget it's suppose to be running commands as ssh and does something local.

Most if not every agent has access to bash or similar, which ssh typically is available. You don't need any bloated skills or anything, as long as you include `host is available via user@10.55` or whatever, and you have authentication properly setup, it'll figure it out.

ytjohn 5mo ago

Confirming that Pi can definitely handles this. I've written a harness "factotum" based on pi just for managing my homelab and my radio club's systems. Has absolutely no issue sshing into things remotely, running ansible/helm/kubectl/talosctl commands. There's a few skills, a and an extension to switch inventory. The extension is only needed because I want to switch between the two organizations. It's pretty slick. One of my use cases was just getting my homelab under control. So one of the first tasks I gave it was to go find everything that's running on these hosts, system services, docker compose, kube pods, etc. Builds an inventory, memory, todos. Switches the script from "ai helps me launch more experiments to lose track of" to "organized and back under config management". .pi/factotum/ ├── active-profile ├── profiles │ ├── club │ │ ├── config.yaml │ │ ├── inventory │ │ │ └── hosts.yaml │ │ └── todos │ │ ├── 22a094a3.md │ │ ├── 427ad844.md │ │ ├── 4c185be7.md │ │ ├── 4d0eea0f.md │ │ └── bcf069a4.md │ ├── examples │ │ ├── config.yaml │ │ └── inventory │ │ └── hosts.yaml │ └── local │ ├── config.yaml │ ├── inventory │ │ └── hosts.yaml │ ├── memories │ │ ├── axel-services.md │ │ ├── fran-mydiffuser.md │ │ ├── fran-services.md │ │ ├── ruffclus-cluster.md │ │ └── ruffclus-paperless-ngx.md │ └── todos │ ├── 0f7fd63e.md │ ├── 75c82ceb.md │ ├── 9cb63594.md │ ├── af33e08f.md │ ├── ba490542.md │ ├── c09c144f.md │ ├── c5f7f8a8.md │ └── d4c4b287.md ├── schemas │ ├── PROJECT_ARCHITECTURE.md │ └── project-architecture.yaml ├── task-templates │ └── host-audit.yaml └── tools └── host_audit_runner.sh

iib 5mo ago
How do you use `pi` to ssh? I use `oh-my-pi`, and tried the `/ssh` command, but I couldn't get it to work. Then I saw a suggestion somewhere to just run `!ssh` to place things into the agent's context. Is there a way to use it like "The current directory is at `ssh server`" and have the agent work from there?

cyanydeez 5mo ago

so, to be clear, is it just doing random bash commands to runn ssh or is it a actual tool, eg, node-ssh command interface. i would not trust bash execution of SSH because it can easily hallucinate local commands instead of remote.

hrimfaxi 5mo ago
> i would not trust bash execution of SSH because it can easily hallucinate local commands instead of remote. Why would it be more likely to hallucinate local commands instead of remote commands if it is in an active SSH session?
- cyanydeez 5mo ago
  I think you're reading into the statement. It can equally hallucinate commands. Fine. The problem is, if I'm working on a remote machine, I'm generally doing things that I'd be less concerned about. If I'm on a VPN and it rm -rf / while I'm trying to clean it up; bad break, but it's not _my machine_ it just removed root on. So if your LLM is just running something like `ssh <remote> "<cmd>"` it could easily foget the ssh <remote> part and suddenly you're modifying your local system. So it's one thing to YOLO on production servers, etc, but wiping out something locally is a significantly different event. Imagine it erasing all your scripts or whatever. Anyway, the point is: I wouldn't trust an agent operating with just a bash cli running ssh commands.
JeremyNT 5mo ago
Background: I use OpenCode to do this. Just tell it to use ssh from the shell. From there you can give it extra context to describe the target (if you know/care about it), or just let it loose and if the environment doesn't have what it expects it will "figure something out" - just the same as with your local env. If there's some least common denominator you know about e.g. python it can streamline things if you tell it to just use that for everything.
- cyanydeez 5mo ago
  I don't think you understand. I'm well aware it can run whatever command on bash. You're taking a significant risk asking it to do what it's doing via ssh, because it could easily forget that it's suppose to be doing ssh and do whatever locally. The point is: opencode should have a specific deterministic tool like https://www.npmjs.com/package/node-ssh https://www.npmjs.com/package/node-ssh where commands can only be run; the environment can only be the remote; etc. The last thing I would want is for it to suddenly forget it's suppose to be running commands as ssh and does something local.