What stops just mentioning AWS/Azure/GCP CLI tools to agents?
That way, it's harder to inject your own business as a mitm dependency in hopes of getting VC funding.
Show HN: Skill that lets Claude Code/Codex spin up VMs and GPUs
41–42 of 42 posts
Re: Show HN: Skill that lets Claude Code/Codex spin up VMs and GPUs
#42Moving agent execution off localhost makes sense for parallel workflows, but giving an LLM direct provisioning power is terrifying from a billing perspective. If the agent gets into a retry loop or hallucination spiral, it could easily spin up expensive GPU instances (like that B200 example) without tearing them down. Do you enforce hard budget caps or instance-count limits at the API key level to prevent runaway provisioning? Also, how do you handle SSH key lifecycle management—are keys rotated per session to ensure no lingering access remains if the teardown command fails?