aspectrr

16 ms·

1. 31.▲
   by aspectrr 8mo ago

   This allows the agent to make any changes in a production clone vs agents running on a production VM. For example, you wouldn't want claude editing crucial config on the chance it brings everything down vs letting it do in a cloned env
2. 32.▲
   by aspectrr 8mo ago

   Sell the shovels!!
3. 33.▲
   by aspectrr 8mo ago

   True. Tried to make it simpler but clearly not a good enough job!
4. 34.▲
   by aspectrr 8mo ago

   Lol, that does sounds a little scary but if it works it works. Mainly I built this to prevent there being a chance that changes affect production. This is meant to be used with scale (say hundreds of VMs) vs 1. From a safety perspective run
5. 35.▲
   Claude Code for Infrastructure(fluid.sh)

   276 points by aspectrr 8mo ago|176 comments
6. 36.▲
   by aspectrr 8mo ago

   Hey HN, My name is Collin and I'm working on fluid.sh ( https://fluid.sh ) the Claude Code for Infrastructure. What does that mean? Fluid is a terminal agent that do work on production infrastructure like VMs/K8s cluster
7. 37.▲
   Show HN: Fluid.sh – Claude Code for Infrastructure(fluid.sh)

   1 points by aspectrr 8mo ago|0 comments
8. 38.▲
   Show HN: Fluid.sh – Make Infrastructure Safe for AI(github.com)

   2 points by aspectrr 9mo ago|0 comments