llamacpp provider does not support API_KEY

Open Beginner friendly
#1,181 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
ai, cli

Research direction

Start by comparing the llamacpp provider with the Chat Completions API provider changes in #1174. Trace how the provider receives configuration and verify that an API_KEY can be passed when connecting to a server that requires one; the bug is done when that connection succeeds.

Written by the indexing model from the issue text.

Description

enhancement
JP version

jp v0.1.0-859ae236 (2026-09-17)

What happened?

The llamacpp provider does not support setting an API_KEY. When the server is configured to require one, jp is unable to connect.

#1174 adds API_KEY support for a Chat Completions API provider. It looks like switching to that provider will resolve this bug.

Dominant language
Rust
Stars
16
Forks
3
Avg merge
1d 1h
Merged PRs (30d)
121

Contributor guide

No contributing guide indexed for this repository

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 dcdpr/jp

All issues in dcdpr/jp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.