Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

New /use-case command to choose a Life Sciences use case

Accounts offered Life Sciences use cases get a /use-case command and a startup dialog to pick one, saved for later sessions

Use it now Notable New Features
JSON All of v2.1.317
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Slash CommandsArea: what it touches
New FeaturesKind: in v2.1.317,
What probably matters to youSection of the release
What

A new /use-case slash command lets you choose the Life Sciences use case that applies to your requests. Slash commands are the commands you type in the prompt starting with /.

  • /use-case followed by a name selects that use case
  • /use-case on its own opens a picker titled "Choose a use case"
  • The choice applies from your next request and is kept for later sessions

A dialog titled "Choose your Life Sciences use case" can also appear at startup when choices are on offer. If you skip it, no use case applies and you are asked again next session.

The command only appears on claude.ai accounts that are offered use cases. It refuses to change anything in these cases:

  • The app that started the session already set the use case
  • Only one use case exists
  • Use cases apply per grant
Why

This only affects accounts offered Life Sciences use cases, but for them it adds both a new command and a new startup prompt.

Read from
Names in the bundle/use-case
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Work with your GitHub repositories touched a line naming /use-case after this was published. Because the prompt asks for either a fix or an explanation, the thread gets an answer even when the behavior turns out to be intended. For more prompts that start from a bug report, see [Fix bugs](https://claude.com/docs/claude-tag/users/u… claude-tag/users/use-cases/work-with-github see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on Work with your GitHub repositories touched a line naming /use-case after this was published.

See this entry in the whole of v2.1.317 →

Feedback