Fluid streamlines the troubleshooting process for Site Reliability Engineers (SREs), Platform Engineers, and DevOps Engineers by allowing them to tackle multiple issues simultaneously. It operates in four distinct phases: read, edit, ansible, and cleanup. In the read phase, Fluid accesses production virtual machines (VMs) using a read-only mode to gather information from logs, system changes, and configurations, helping to identify issues. The edit phase involves creating a sandbox by cloning the original VM. Engineers can experiment with changes in this isolated environment without affecting production. After resolving the issue, Fluid generates an Ansible playbook in the ansible phase, which can be used to apply the same fix to the production environment. Finally, during the cleanup phase, any open sandboxes can be deleted either automatically when the Fluid command-line interface (CLI) closes or manually by the user. Installation of Fluid is straightforward. Users can set up the terminal agent on their local workstation with a simple command. For managing multiple agents and sandboxes, there's an API version available. Fluid also emphasizes sandbox isolation, context-awareness, and a full audit trail, ensuring that every command and change made is logged, which aids in maintaining reproducible infrastructure. The ability to auto-generate Ansible playbooks from sandbox work enhances reproducibility and efficiency in managing infrastructure changes.