Looks pretty good and is quite fun to play, but for some reason the manager always told me the exact commands to achieve the tasks instead of just letting me do them by myself. I couldn't tell whether there was a specific option to take on the challenge on my own, as the demo on GitHub showcases.
I've added a "No command hints" option on the start screen: the manager only says what the result must be, and you have to figure up the solution by yourself.
I've been building out my ground up fully automated software development platform for ... Over a year now, albeit with a hard pivot around April this year.
And treating the whole stack as part of the same system and enforcing everything to be automated and consequently adding more and more quality gates feels just like unlocking technologies in eg factorio, introducing new archetypes feels just like building new outposts etc
It just keep getting bigger and bigger with more and more features I've ever thought of in my professional life, provided by the platform, built entirely by agents (since the hard pivot).
Like Auto-Generating consumer pacts, providing them in a repository server pinned by service version. Then pull those in from the deployment orchestration to be verified again those as a quality gate on deployment.
And providing the providers response to those pact as software packages themselves, and pulling those in on the consumers for e2e tests across the stack - right down to screenshot tests in the UIs...
And from those dependency trees building optimal release trains for the least amount of releases (bunching up software changes with lib version bumps etc)
It's definitely the sort of thing that starts out simple and just grows and grows and grows. The hardest part is avoiding false positives on the various gates that I put in with the best intentions. Finding the right balance between making the factory safe and keeping production running is literally the hardest part.
Why are we all building more or less the same thing? Is it what we want, or what the models want, or is this some human end-pattern singularity-esque thing? Why are we all asking this same-ish question?
I've added the local LLM support per your feedback!
Just set `LOCAL_LLM_URL=http://127.0.0.1:11434/v1` and pick "Local" on the start screen.
Any OpenAI-compatible server works (Ollama, llama.cpp, vLLM).
Details in the README at "Local models" section.
I swear, one of the weirdest things about big corporations is how people believe that all the important decisions affecting them are made in the boardroom.
They overwhelmingly aren't. We build our own hell: 99% of product decisions in places like Google or Microsoft come from your peers, line managers, and PMs. Your manager may talk to the top brass a couple of times in their life. Even big-ticket decisions like "we need to lay off 10%" don't really come from execs, they come from some mid-level guy in finance who says "our quarterly numbers are not looking too great" - and even more uncomfortably, from the implicit, cumulative pressure from employees who want the value of their stock grants to keep climbing or they will start interviewing elsewhere.
I have some recent insights from a company that executed an "everything must be AI" pivot and sat in some of the department strategy meetings. It was mostly line employees who came up with ideas such as "we need a dashboard to show token use across departments and give that to managers come performance review time". In the meantime, another AI maximalist faction was telling the execs (or outright lying, if you prefer) that the technology enabled them to 100x and it would be crazy not to mandate it.
Execs bear the blame insofar that they foster this sycophantic, over-eager corporate culture, but ultimately, the call is coming from inside the house.
> It was mostly line employees who came up with ideas such as "we need a dashboard to show token use across departments and give that to managers come performance review time".
I'm a bit confused by this game. What's the output format? Does the manager-LLM read all of my commands or just my report? Subagents usually send messages back - here the manager reads all commands?
I legitimately do something like this to help debug and improve my LM systems. I hijack the network requests and try to answer it manually based on the context.
It’s useful to put yourself in the models’ place to understand what they can or cannot do.
I can see myself playing this to unwind from a long day at my job as an llm jockey. And that’s exactly why I won’t play it. The irony would be too much for me.
Finally, a role I can put on the org chart without a reorg. Does the game punish you for vague instructions from the orchestrator? That is the realistic part I would want modeled.
I particularly like that it's broken, barely-playable AI slop, which is the only kind of hobby projects that HN likes nowadays - thus unintentionally adding a second layer of meta-commentary.
This is actually better/worse than the Matrix, depending on what you value. In the Matrix, you usually have no idea that you're really just being used as a battery and are free to "do" whatever you want in VR. As a subagent, you're aware of what you are and that you need to do any assigned work and do it well because your review - and continued existence (not being picked is akin to not existing) - depends on it.
I've added a "No command hints" option on the start screen: the manager only says what the result must be, and you have to figure up the solution by yourself.
Isn't that just the best factory game ever?
I've been building out my ground up fully automated software development platform for ... Over a year now, albeit with a hard pivot around April this year.
And treating the whole stack as part of the same system and enforcing everything to be automated and consequently adding more and more quality gates feels just like unlocking technologies in eg factorio, introducing new archetypes feels just like building new outposts etc
It just keep getting bigger and bigger with more and more features I've ever thought of in my professional life, provided by the platform, built entirely by agents (since the hard pivot).
Like Auto-Generating consumer pacts, providing them in a repository server pinned by service version. Then pull those in from the deployment orchestration to be verified again those as a quality gate on deployment.
And providing the providers response to those pact as software packages themselves, and pulling those in on the consumers for e2e tests across the stack - right down to screenshot tests in the UIs...
And from those dependency trees building optimal release trains for the least amount of releases (bunching up software changes with lib version bumps etc)
https://avneeshk.me/you-are-the-model/
They overwhelmingly aren't. We build our own hell: 99% of product decisions in places like Google or Microsoft come from your peers, line managers, and PMs. Your manager may talk to the top brass a couple of times in their life. Even big-ticket decisions like "we need to lay off 10%" don't really come from execs, they come from some mid-level guy in finance who says "our quarterly numbers are not looking too great" - and even more uncomfortably, from the implicit, cumulative pressure from employees who want the value of their stock grants to keep climbing or they will start interviewing elsewhere.
I have some recent insights from a company that executed an "everything must be AI" pivot and sat in some of the department strategy meetings. It was mostly line employees who came up with ideas such as "we need a dashboard to show token use across departments and give that to managers come performance review time". In the meantime, another AI maximalist faction was telling the execs (or outright lying, if you prefer) that the technology enabled them to 100x and it would be crazy not to mandate it.
Execs bear the blame insofar that they foster this sycophantic, over-eager corporate culture, but ultimately, the call is coming from inside the house.
Were they technical employees or nontechnical?
I've only ever seen technical employees campaign for worse working conditions.
https://en.wikipedia.org/wiki/Paperboy_(video_game)
It’s useful to put yourself in the models’ place to understand what they can or cannot do.
Like pilots having mandatory flying, this can be a programmers mandatory coding time.
Turns out it was a common Unix permission set :)
LLMs might go down in history as the most extreme example of this type of failure to align with reality.