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.
I wrote a little wrapper to start tmux with two panes open, one pane is an ssh connection to a host and one runs Claude Code, with an auto-generated CLAUDE.md telling Claude to use tmux commands to interact with the remote host (https://github.com/swelljoe/tandem). Agents can also use ssh, but I wanted an interactive way to poke around on a remote system and also be able to ask Claude to look at or do something on its own without copy/paste.
I was looking at warp, wave, and a few others, and this is the exact stuff I will need, thanks for sharing.
So when I SSH to remote servers, I would like to bring my agent buddy with me, currently, I open two terminals, one with a remote SSH session, and one with opencode/claude code, now I have to copy & paste commands/info between the 2 terminals, which can be anoyying, so that is why I was looking at warp, but it has a paywall for BYOK :)
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.
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 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 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.
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.
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.
That was exactly my question; why fork? I assumed the project owners were preserving their business model, but if you allow it to be opened-up and turn off the cloud features, I see no reason to fork.
Makes plenty of sense to upstream this (possibly makes more more than forking, although I suppose it's one way of gauging interest and implementation complexity).
Let me tell you a disturbing fact. The open source warp does not even have prompts. It is completely cloud-based, including the calling process of various tools in oz cloud. So I think it is better to change than to wait.
Despite the newish "AI" branding for what I would presume is marketing buzz reasons, most of Warp is really centered around trying to make a terminal interface not anchored to legacy assumptions, like the blocks functionality (https://docs.warp.dev/terminal/blocks).
This page doesn't tell me anything useful about what this feature does or how it works. The attached screenshot is pointless. I assume the actual information is in the embedded Youtube video. YouTube is not an acceptable alternative to written documentation