WSUG: Web Services User Group at Drexel University
Published:
Please feel free to join and collaborate with our Web Service User Group (WSUG) members on our Google Group.

Professor, Author, Machine Learning Researcher, Educational Consultant, and Scholar of Teaching and Learning; Host: digitalsignature.fm
less than 1 minute read
Published:
Please feel free to join and collaborate with our Web Service User Group (WSUG) members on our Google Group.
12 minute read
Published:
Once more than a dozen coding agents were installed and running side by side under Herdr, as I describe in Herding Agents, the work shifted from running them to coordinating them: deciding which agent does which job, making sure a job survives when one agent hands it to another, and keeping experiments away from anything that matters. I rely on three things for that: one agent that supervises the others, a shared job board that any agent can pick up from, and throwaway containers for anything risky. The post ends with the working rules that keep the whole arrangement safe.
11 minute read
Published:
This term, every student in my class has their own Linux VM on Jetstream2, an NSF-funded research cloud available through the ACCESS program. Educational use is free. I use the VMs to run agentic coding tools such as OpenCode inside Docker, so students do not have to install anything on their laptops and I do not pay for cloud machines myself.
99 minute read
Published:
Coding agents are useful because they can read your files and run commands. That also makes them risky to run on a machine with real data on it. A model can misread an instruction, or a file it opens can contain instructions of its own, and an agent running as you can do anything you can do. I run several agents at once, and each one wants access to the same drives. I’d like them to cooperate without all of them being able to see everything.
42 minute read
Published:
I now run thirteen coding agents side by side on a small always-on Ubuntu server: Claude Code, Codex, Antigravity, Grok Build, Hermes, GitHub Copilot, two separate copies of OpenCode, pi, Oh My Pi, Kiro, Mistral Vibe, and Meta Muse. Herdr keeps them organized, one labelled tab per agent, and brings them back after a reboot. Most of them share one mcpproxy instance for tools. One of those tools talks to a service that needs a personal API key, and only one agent ever holds that key: a deliberately fenced-in OpenCode. The other agents can see the tool, but they can’t authenticate to the service behind it. When they need that service, they hand the task to that OpenCode through Herdr.