I’ve been using Steve Yegge’s Beads[1] lightweight issue tracker for this type of multi-agent context tracking.
I only run a couple of agents at a time, but with Beads you can create issues, then agents can assign them to themselves, etc. Agents or the human driver can also add context in epics, and I think you can have perpetual issues which contain context too. Or could make them as a type of issue yourself, it’s a very flexible system.
This is a machine that runs a custom Linux OS, "designed for work" by some pretty talented people. Not sure what to think but there are some interesting possibilities.
Drupal CMS is designed to be easier to set up than Drupal Core, with such "batteries included" as data privacy protection (GDPR, cookies etc), multilingual tooling, improved accessibility, automated security updates, and a "recipes" feature for quickly adding features.
From the repo: “A fast, privacy oriented meta search engine that just works. Kept simple so everyone can use it and to make sure it works on most (basic) web servers.”
I mean, I've worked for several companies and left months before they actually launched. Any contractor who works with startups have been through similar situations.
Not that much. Apache gets about 30-40 requests per second on average. However, this is with Varnish handling a lot of requests that never get sent to the backend.
I only run a couple of agents at a time, but with Beads you can create issues, then agents can assign them to themselves, etc. Agents or the human driver can also add context in epics, and I think you can have perpetual issues which contain context too. Or could make them as a type of issue yourself, it’s a very flexible system.
[1] https://github.com/steveyegge/beads