[FEATURE] Opt-in mechanism for users to share use cases / impact stories

Resolved 💬 2 comments Opened Mar 13, 2026 by JasonWildMe Closed Apr 11, 2026

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

As a user doing applied work with Claude Code, I'd love a lightweight way to flag "this is a meaningful use case" back to Anthropic — an opt-in channel for surfacing real-world impact stories from the field.

The gap

During a conversation, Claude noted that it has no outbound channel to surface anything to Anthropic. Everything stays in the conversation. This means Anthropic's product and impact teams have limited visibility into the most compelling real-world applications unless users proactively reach out.

Meanwhile, the users doing the most interesting work may have no way to reach Claude's impact, outreach, and social good teams.

Proposed Solution

A simple opt-in mechanism, something like:

  • A /share-use-case slash command that lets users draft a short description of what they're using Claude Code for,

which gets submitted to Anthropic

  • Or a periodic optional prompt: "Would you like to share what you're working on with Anthropic?"
  • Or even a simple thumbs-up/tag system on conversations: "This conversation was impactful for [conservation /

research / education / ...]"

Design considerations

  • Must be user-initiated and opt-in — Claude should never report back without explicit user consent. Trust that

conversations are private is foundational.

  • Low friction — if it takes more than 30 seconds, nobody will use it
  • Structured enough to be useful — domain tags, a one-liner, and optional detail would let Anthropic's team aggregate

and discover patterns

  • No conversation content shared by default — the user describes the use case in their own words, rather than

forwarding transcript data

Why this matters

Anthropic talks about wanting AI to be beneficial. But the feedback loop for how it's being beneficial is mostly
anecdotal — Twitter posts, occasional case studies, word of mouth. A lightweight opt-in channel would:

  1. Surface use cases Anthropic would never otherwise hear about (wildlife conservation, marine biology, field ecology)
  2. Help the product team understand which features matter most for applied research
  3. Create a pipeline for impact stories that demonstrate Claude's value beyond software engineering
  4. Give users who care about Anthropic's mission a way to contribute back

Alternative Solutions

Trying to email, tag Anthropic on social media. Should outside very loudly.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

I'm the Chief Data Officer at https://wildme.org (part of Conservation X Labs), where we build open-source computer vision for wildlife conservation. We operate Wildbook installations worldwide for endangered species monitoring.

Over the past several months, I've been using Claude Code extensively to:

  • Develop and debug animal re-identification models (think facia recognition for wildlife)
  • Train YOLO object detectors for new species
  • Build data pipelines between Wildbook and our ML training workflows
  • Accelerate feature and fix delivery for 2500+ wildlife biologists tracking 320,000 individuaal animals

Claude Code has become a genuine research partner in this work — not just generating code, but helping reason through ML experiment design, reviewing papers, debugging CUDA training runs, and building domain-specific skills and MCP servers.

I would love to type /share-with-anthropic to help raise awareness for our work, and likely other users would have similar use cases to share and highlight around social good.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗