HN Explorer

11 comments

[ 0.26 ms ] story [ 27.7 ms ] thread
radim_h
Quite interesting setup. How are you handling credentials and external API access for the agents, when different agents do need different access?

Are they running with the same permissions as the host, or do you isolate them and give each workflow its own access?

gojkoa
This is a minimal boilerplate so that part was excluded but in the real setup this was extracted from we use AWS SSO from the CLI to authenticate against AWS (short-lived tokens) and the keys for other things are in the AWS SSM parameter store as secure strings (encrypted), locked down with IAM so that agents can only access specific (test) keys while developing.

The agents are running inside a docker container (this is part of the setup) and only share the workspace and tmp dirs with the host. They run under user permissions in the container, not root.

zacharyvoase
What does lights-on mean?
rcxdude
opposite of 'lights-out', which in factory terms means a factory that's sufficiently automated that it can operate most of the time with the lights turned off because there's no people inside.
dbbk
Are people supposed to know this?
SyneRyder
It is becoming common nomenclature. I think I first heard about Dark Factory / "lights-off" in AI about a year ago now.

There's a similar concept in food delivery, where restaurants that only deliver food (eg Doordash / Uber Eats only) and don't have a physical store for customers are called Dark Kitchens. They try to automate as much of the food preparation as well.

gojkoa
humans supervising agents, not dark factory where agents supervise agents. providing a very high degree of automation, not fully automated. controls implemented using deterministic tools, not via markdown prayers.