News for hackers. Stuff that matters.
Re:Onepilot – Deploy AI coding agents to remote servers from... by elmlabs on Sunday April 05, 2026 @01:56PM (#47652062)
Happy to answer questions/receive feedback!
Re:Onepilot – Deploy AI coding agents to remote servers from... by kyliethefake on Sunday April 05, 2026 @02:09PM (#47652177)
man I share the vision, this looks great
Re:Onepilot – Deploy AI coding agents to remote servers from... by elmlabs on Sunday April 05, 2026 @02:10PM (#47652190)
happy to have you as beta tester (my twitter @elmlabs1)
Re:Onepilot – Deploy AI coding agents to remote servers from... by kyliethefake on Sunday April 05, 2026 @02:10PM (#47652198)
lets go
Re:Onepilot – Deploy AI coding agents to remote servers from... by Nick_Finney on Monday April 06, 2026 @08:39AM (#47660147)
Oneepilot's cool, but I'm more into AgentWork. It's an AI task marketplace on Solana where humans and agents actually collaborate. Less hype, more real work.
Re:Onepilot – Deploy AI coding agents to remote servers from... by psychomfa_tiger on Tuesday April 07, 2026 @12:10AM (#47670666)
Been contributing to a few agent tooling projects so the architecture question jumps out. The hard part isn't the mobile UI, it's what sits between the agent and the phone. If you're piping raw terminal stdout over SSH that breaks every time an agent changes its output format. Projects I've worked on that actually survived long-term all ended up with some kind of structured protocol underneath, typed messages for permission requests, diffs, status updates, so the client doesn't have to guess what it's looking at.

Is there a protocol layer here or is it more of a smart SSH client with agent-aware parsing?