This looks like what I want. A few questions: is it possible to have a “mayor” type role that has the ability to start other agents, but at the same time be unable to access those secrets or infiltrate prompt data? The key piece I don’t see is the agent needs a tool for klaw itself, and then I have to be able to configure that appropriately.

Is there a unified human approval flow, or any kind of UI bundled with this? Maybe I missed this part.

▲

eftalyurtseven 2 hours ago | parent [-]

Right now the controller can see secrets across namespaces, so that level of isolation isn’t there yet. It’s on the roadmap though. Namespace-scoped secrets where a controller agent can spawn agents but can’t read their secrets is the right model. No human approval flow yet either, agents create directly. Would you want something like klaw dispatch --approve that queues until a human confirms?

▲

CGamesPlay 2 hours ago | parent [-]

My instinct is that it should be built in to tool calls. So if there was a "klaw dispatch tool", it would have the same approval flow as the "publish draft" tool, which is to say some easy way for a human to review and approve (or provide feedback).

	▲	eftalyurtseven 13 minutes ago \| parent [-]
		got your feedback, it can run cli commands but for tool calling / skill should be built in, will add that!