Custom Workflows: Missing visual feedback after loading workflow

[jeremyeder]

Problem

When loading a custom workflow, there are multiple missing visual indicators and UX issues that make it unclear whether the workflow was successfully loaded and which workflow is currently active.

Key Issues Identified

1. No colored badge on the Workflows accordion - Expected to see a visual indicator showing which workflow is active
2. No confirmation message after loading - No indication that the workflow was "discovered, linted, and successfully loaded"
3. Generic "Custom Workflow" label - Doesn't show which specific custom workflow is loaded
4. No validation during load - Linting should happen in the modal before it closes
5. Missing workflow metadata - Should display the description from ambient.json
6. No workflow switching capability - Can't easily see or switch between loaded workflows

Current Behavior

• User loads a custom workflow via the "Load Custom Workflow" dialog
• Workflow loads successfully in the background
• No visual feedback on success/failure
• User must manually verify in chat which workflow is active
• Uncertainty creates feeling that "something might be broken"

Expected Behavior

Workflow Loading & Validation

• Lint during load: Validate ambient.json structure, check required fields, verify file accessibility
• Actionable error messages: If linting fails, provide helpful guidance (e.g., link to GitHub integration docs for private repos)
• Success confirmation: Clear message when workflow loads successfully

Workflow Display & Switching

• Accordion shows all workflows: Both built-in and custom workflows listed
• Display actual workflow names: Use the name from ambient.json, not generic "Custom Workflow"
• Show active workflow: Clear visual indicator of which workflow is currently active
• Display workflow description: Show the description field from ambient.json in the UI
• Enable workflow switching: Allow switching between workflows while preserving session context (uploaded files, workspace state)

Fallback Workflow

• Always have a workflow active: Include a "Basic Chat" or default workflow as fallback option

Rationale

As noted by the user: "A workflow changes the personality of the session. It is critical to know which workflow is currently in effect."

Without clear feedback, users:

• Don't know if the load succeeded or failed
• Can't tell which workflow is active
• Feel uncertain and think they might have broken something
• Have no way to switch between workflows in a session

Steps to Reproduce

1. Click "Load Custom Workflow"
2. Enter repository URL, branch, and path
3. Click "Load Workflow"
4. Observe lack of visual feedback
5. Try to determine which workflow is active (currently requires asking in chat)

Related Improvements

• Better integration authentication UX (GitHub, Jira, Google, etc.)
• Integration wizard/agent to set up all integrations in bulk
• Improved documentation for using integrations

Impact

Users are left uncertain whether their workflow loaded correctly and have to manually verify through chat interaction. This creates friction and reduces confidence in the custom workflow feature.