I would like to run a single Vessel in the Fleet by itself so I can test that it works correctly without having to build it outside of the Fleet.

I would like the ability to run a fleet starting at any specific Vessel. It's perfectly fine if that Vessel is started with no upstream data.

I would like the same features as "Build with AI" for Python, but for Bash.

Maybe in the same organization we have different teams, like finance, it, engineering, etc. And when storing credentials at a org level maybe these don't want to be shared across all teams.

On the Fleet Builder view, give the ability to move the divider left/right so that the canvas or Vessel editing screen can be expanded.

I would like the ability to set Environment Variables at the Fleet level. This way, I could set a variable like $FILE_NAME and use it as an input on every Vessel. If I wanted to change the file name, I would only have to update it in one location.

On the credential pages, I would like to see which Vessels are actively using the credentials so that I can have more confidence which Vessels are going to be impacted by me removing or updating a credential group.

I would like to have a dashboard that shows me a high level view into everything running on the platform. Recent runs, recent failures, recently created, etc.

I would like the ability to have a Fleet in a "draft" state where I can make changes without any issues. Once I've verified all of my changes will work, I can promote the draft to a new version of the Fleet. The only way to accomplish this currently is to duplicate the current Fleet, make edits I need, then either copy/paste the edits over to the existing Fleet... or just remove the old Fleet (which removes version control/log history).

As an admin, I should be able to set an option that allows myself, or another user, to access all future created projects, rather than needing to continuously give myself access to new projects.