Long overdue - I was all in a few years ago with Warp, but after the last couple of years of not addressing this need, I have moved on from Warp. I now DO NOT see the need to embed AI into the terminal when you can have all sorts of TUI doing the same job.
What about when SSHing to an external server, or working in a container?
Hand your agent a tmux session.
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.
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".
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?
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.
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.
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.
> 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?
This might have changed but Warp was not able to do this without “warpifying” the SSH host.
I mean… Claude Code desktop will SSH into anything and start coding for ya. Which could sound horrifying but if you setup an isolated system for that specifically its not that horrifying.