Validate the Anthropic Claude AI provider with a real API key

Open Beginner friendly
#810 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
70/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
ai, testing

Research direction

Start by reading the AI guide at docs/src/crates/ai.md to see how the Anthropic Claude provider is configured with the ai feature. Then run the three checks in a new project: a plain prompt, a structured-output request and a streamed response, confirming the prompt-injection filter and PII masking still apply. Done means each step's result, with any error text and the Rullst version, is posted in the issue and the guide records a dated successful run.

Written by the indexing model from the issue text.

Description

good first issue help wanted

rullst-ai's Anthropic Claude support is tested offline only (mock mode); it has never answered a real request.

Comment "I'll take this" before starting, so two people do not test the same thing. Use a free tier or trial where one exists, and delete what you created afterwards.

What to do

  1. Create a Anthropic Claude API key with a small spending limit.
  2. In a new project, enable the ai feature and configure Anthropic Claude as the AI guide shows.
  3. Send a plain prompt, a structured-output request and a streamed response; check the prompt-injection filter and PII masking still apply.

Documentation: AI guide

What to report (comment here)

  • Rullst version, operating system, and the plan or tier you used.
  • Whether each step worked, and the exact error text for anything that did not (remove secrets first).
  • Anything in the documentation that was wrong, missing or confusing.

Never paste API keys, client secrets, tokens or connection strings into the issue; keep them in your local .env. Bugs go in a bug report; fixes to the docs can be a pull request. A successful run is recorded in the documentation with its date, and the integration moves up on the website's "How far each integration has been tested" list.

Part of #801.

Dominant language
Rust
Stars
21
Forks
6
Avg merge
5h 35m
Merged PRs (30d)
246

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rullst/Rullst

All issues in Rullst/Rullst

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.