Validate the Anthropic Claude AI provider with a real API key
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 70/100
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
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
- Create a Anthropic Claude API key with a small spending limit.
- In a new project, enable the
aifeature and configure Anthropic Claude as the AI guide shows. - 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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Rullst/Rullst
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Validate the Ollama AI provider with a real serverPossibly taken @visy-ani claimed this today. Opengood first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 70/100
Rullst/Rullst#812 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
eventflux-io/eventflux#203 ·
Maintainers usually reply within 1 day
-
bug ui
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
userFRM/egui-charts#4068 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
trezor/trezor-firmware#8357 ·
Maintainers usually reply within 2 days
-
fuzz-crash review-followup
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day