upvote
Couldn't agents just Remote Desktop or ssh into them?

For seriously older stuff, I'd run the disk image in a VM.

If they interact with legacy systems and/or virtualizing is no option and/or they have no internet access, a simple USB-to-COM adapter can create wonders. I remeber doing that on a win3.1 machine using TERMINAL.EXE many many years ago.

reply
In general, I've wondered whymost (all?) harnesses perform the API calls to the provider from the same machine that runs the tools. Why not have a client/server architecture? Then one session could talk to as many tool harnesses as it wanted to and you wouldn't have this kind of arbitrary limit of the session being tied to one specific workspace.
reply
My harness actually has 3 distinct components: the LLM gateway, the agent session manager, and the tool server, and they can be run on different machines. The most obvious use case is the LLM gateway being a central router for all provider queries with multiple machines running the agent sessions.

The agent session manager talks to the LLM gateway over HTTP using a standard internal protocol, then the gateway has adapters for each upstream provider and translates between their external API format and the standard internal one.

The tool server is a separate jar running as a separate server process with its own systemd unit and the agent session manager talks to the tool server over a beanstalkd queue. The primary motivation for having 2 processes was total separation for unprivileged agent tool call execution (ie. the tool server systemd unit runs as a user with no sudo whereas the agent session manager can execute as root, so the user can run scripts through the interface that do things like install packages and access secrets, but the agent can't do that.

The tool server could just as easily be talking to beanstalkd over a Cloudflare tunnel or ssh port forward, though, and a session could be routed to different machines, allowing execution of tool calls in different environments within the same context window/agent session.

reply
[flagged]
reply
A typical scenario is that you walk into a small company and find they're still using Windows 7 or an early version of Windows 10. Then you have to help them deal with all sorts of problems.
reply
https://github.com/xmeadow/igor runs on react OS but was tested on XP and win7. Works flawlessly.
reply
Offtopic, but: do you daily-drive ReactOS? If so, care to share the experience -- any recurring hiccups, etc? Thanks.
reply
I wonder what kind of sandboxing you'd get on those machines though. Likely nought.
reply
Sandboxing would defeat the point of using agents on these machines, though.
reply
I've got an agent that just uses legacy perl 5.0001 ... close but there's no perl by default on windows (although it's easy enough to get on there)

https://github.com/kristopolous/old-agent

I've used it on plenty of old things.

I'd probably do a pure .vbs version if it was windows or a static pure win32 exe.

reply
Neat concept. I enjoyed the screenshots.

I took the same path with my for-fun/learning GUI coding agent in Tcl/Tk: https://wiki.tcl-lang.org/page/Featherweight. It shells out to curl for the networking.

I've just tried to get it to run on Windows XP SP3. (I have a VM for an old Canon all-in-one printer.) I grabbed a legacy Tcl 8.6.6 installer from https://github.com/dbohdan/tcl86-nsis-installer (mine) and a 2017 build of curl with certificates from https://winampplugins.co.uk/curl/. The harness was developed against curl 8 and didn't work with 7.53.1. MiMo-V2.6-Flash, running in the same harness on modern Linux with Wine for `curl.exe`, found that the necessary change was minimal and only touched `--write-out`:

  --- featherweight.tcl
  +++ featherweight.tcl
  @@ -2794,7 +2794,8 @@
               --request POST \
               --show-error \
               --silent \
  -            --write-out "\n%{http_code} %{exitcode} %{errormsg}" \
  +            --write-out "\n%{http_code} 0" \
               [dict get $config endpoint] \
Here are two screenshots of the result. Featherweight is running in Tcl 8.6.6 on Windows XP.

https://paste.dbohdan.com/1ng3b5y-kb4yd/greenshot-1.png https://paste.dbohdan.com/1ng3b5y-kb4yd/greenshot-2.png

reply
Instead of Curl get IronTCL and use http://legacyupdate.net to update the certs.
reply
I need HTTP proxy support in Featherweight. I have found shelling out to curl easier and more reliable than a stack of `http`, `tls`, and `autoproxy`.
reply
My Free Pascal / Delphi agent compiles to a huge amount of platforms and no NodeJS required. I haven't tried targeting older platforms specifically but I do run it on Windows 10 and Windows Server 2019.

https://github.com/FMXExpress/PasClaw/

reply
I've been working on a coding agent called Psi[0] (port of Pi) that is written entirely in ANSI C and Lua, MIT licensed. Tested on Linux, macOS, Windows, Haiku, BSD. The first three being the same executable too running via cosmopolitan libc. Otherwise it just requires a POSIX environment.

[0] https://psicode.ai/

reply
Almost all agents require Windows 10 1809 or later. Debugging issues on older devices often turns out to be a real headache, and the only option is to get SSH working.
reply
There are Golang ports for WXP and up (check the Reticulum-go GH repo and the users), and there's MIn-C as a port of core OBSD tools for XP (Unix tools, compiler, vi, openssh and a bunch more).
reply
But should not AI be able to solve all these mentioned problems? Why can they not solve that?

It would not make a whole lot of sense to me.

reply
For old Windows, "setting up an SSH tunnel" itself takes quite a bit of fiddling. Especially when the device you need to deal with is on a distant external network, and you can't even remote in—you're limited to video calls and the like.
reply
Agreed. Kind of strange how AI promises everything but the old platforms are still ignored and neglected.
reply