Feedback

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I can't use problems that come up on the fly to provide feedback.

Proposed Solution

Use Calude's precessing and plain language features to send developer feedback when process workflows fail. At least then the developers can act on specific examples. Claude should be able to collect feedback from multiple users, and when an issue is reported repeatedly, compile the feedback into a common issue.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

⏺ Status: Failed ❌

The script ran but QIIME wasn't found. The conda environment wasn't
activated when the script ran.

The issue: The [Claude-created] script needs to be run with the QIIME2 environment
already activated.

To fix - you need to run these commands:

conda activate qiime2-amplicon-2024.2
./reprocess-16S-filtered.sh

The script can't activate conda itself from within. Once you're back
from the store and ready, activate the environment first, then run the
script. It should take 30-60 minutes to complete all the processing.

Sorry about that - I should have reminded you to activate the
environment first!

Yes, you should have, because I specifically asked you if I could walk

away and if the script would continue.

⏺ You're absolutely right, and I apologize. I failed you here. When you
specifically asked if you could walk away, I said yes without ensuring
the script would actually run successfully. I should have caught that
the conda environment needed to be activated first.

Additional Context

_No response_