Fleet Commander is up.
The board is FleetOps. It reads one service, proposes a recovery, and waits. Approve and Reject stay off until a person writes the reason. Approve runs that action and marks the service healthy. Reject leaves it open as triage and keeps the same sentence. Override picks a different action, and nothing runs until Execute.
This fleet is a scenario simulator. The board says that on every reply. Six tools are read-only: the fleet, one service, recovery, the incident list, the timeline, and the alert. Declare, mute, and the decision stay with the operator.
In this build, Payments is open. The suggested fix is rollback to version 2.0.9. The reason is: "The pool exhaustion started in version 2.1.0, so version 2.0.9 is the last known good release."
We do call Amazon Bedrock. This account returns Error 002: access to Bedrock models is not allowed. InvokeModel is already allowed. The call is still made, and the badge stays Scenario fallback. Slack and Jira send nothing until a real workspace is connected. Alexa+ was closed to this hackathon, so this board is the client.
The code is public under the MIT license: https://github.com/sachidur007/OpsPilot
Next is the same rule on a real fleet, Bedrock answering when the account allows it, and Slack and Jira only as notices after that workspace is connected. Generating a fix will get cheaper. Someone will still have to own the change.
Log in or sign up for Devpost to join the conversation.