top | item 47029407

(no title)

eftalyurtseven | 14 days ago

Mostly the second, plus fleet management. Each agent runs in an isolated namespace with its own config, channels, and skills. You manage them declaratively like you would pods, but the unit of work is an AI agent instead of a container. The Kubernetes analogy is about the operational model: clusters for org isolation, namespaces for team isolation, declarative deploys, central monitoring. Not about hardware scheduling. I'll improve the README to make this clearer, good feedback.

discuss

order

fudged71|14 days ago

Is there any current solution elsewhere for hardware scheduling?

eftalyurtseven|14 days ago

Yes, klaw has a controller-node architecture. You join machines to a cluster with klaw node join and deploy agents to specific nodes.

I added distributed agent management functionality