@OpenAIDevs For the past 3 weekends I've been building https://t.co/TPiGGknYBK, a remote control plane for local coding agents. This weekend I added openai in front of it and made it into a remote agent orchestrator.
@gdb For the past 3 weekends I've been building https://t.co/TPiGGknYBK, a remote control plane for local coding agents. This weekend I added openai in front of it and made it into a remote agent orchestrator.
This weekend I forked @OpenAI#Codex and added the #WebSocket connector from Span's #AgentLink to the #TUI. Now an interactive terminal's output can be pushed to #Span (https://t.co/pyXVYC0XFQ) and resumed later from a remote session.
#KeepOnHacking ๐พ
The WebSocket daemon (AgentLink) is #OpenSource for transparency while the front end acts as a control plane for the infrastructure to retain your agent history, provide lifecycle management, io stream, and make your agents available to you wherever you are
I wanted to keep @OpenAI#Codex working on my dev machine while I was away, without screen sharing or remote desktops. So I treated agents like remote workers with scoped permissions, long-running state, and observable output by creating a remote orchestration layer.
@OpenAI Now I can be away from my dev machine and keep an eye on the agents while they still work. It also supports spawning #GeminiCLI & #ClaudeCode instances ๐
@ryancarson its not a social media platform, but if you're interested in a platform that intelligently replaces your resume with a living profile that's honest and meritocratic: https://t.co/h5VWv2yZth