docs(agents): add LLM API provider guide in app/services#1135
docs(agents): add LLM API provider guide in app/services#1135muddlebee merged 2 commits intoTracer-Cloud:mainfrom
Conversation
|
🤖 CI passed. Linter didn't scream. Reviewer typed LGTM. @muddlebee, every machine in this pipeline just slow-clapped. 🖥️✨ 👋 Join us on Discord - OpenSRE : hang out, contribute, or hunt for features and issues. Everyone's welcome. |
Greptile SummaryThis PR adds
Confidence Score: 4/5Safe to merge after fixing or removing the misleading external link in app/services/AGENTS.md. A single P1 issue exists: the "primary reference" URL points to an unrelated product, which would actively mislead contributors following this guide. All file references and steps are otherwise correct. No code paths are affected. app/services/AGENTS.md — the docs.openclaw.ai link on line 9 needs to be removed or replaced. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Developer adding a new LLM provider] --> B{Provider type?}
B -->|API / HTTP| C[app/services/AGENTS.md]
B -->|Subprocess CLI| D[app/integrations/llm_cli/AGENTS.md]
C --> E[app/config.py\nLLMProvider literal + env vars]
C --> F[app/cli/wizard/config.py\nSUPPORTED_PROVIDERS metadata]
C --> G[app/services/llm_client.py\nLLM_PROVIDER → client routing]
C --> H[app/cli/wizard/env_sync.py\n.env key sync]
E & F & G & H --> I[tests/services/ + wizard tests]
Reviews (1): Last reviewed commit: "docs(agents): cross-link LLM API guide f..." | Re-trigger Greptile |
|
|
||
| Primary reference for provider discovery: | ||
|
|
||
| - [https://docs.openclaw.ai/providers](https://docs.openclaw.ai/providers) |
There was a problem hiding this comment.
Unrelated external link cited as primary reference
docs.openclaw.ai is the documentation site for OpenClaw, a personal AI assistant product (inbox clearing, email sending, calendar management via WhatsApp/Telegram). It is not affiliated with this project. Pointing contributors to an unrelated product's provider catalog as the "Primary reference for provider discovery" is misleading — a developer following this guide would land on documentation that has nothing to do with opensre's provider wiring.

Fixes #
Describe the changes you have made in this PR -
Adds
app/services/AGENTS.md: a short guide for extending API-backed LLM providers (wherellm_client.pyandLLM_PROVIDERwiring live), with a pointer to CLI work inapp/integrations/llm_cli/AGENTS.mdand OpenClaw’s provider catalog for discovery.Single-file change only — no sample templates, no code paths.
Demo/Screenshot for feature changes and bug fixes -
Documentation-only. No UI. Proof: review
app/services/AGENTS.md(37 lines).Code Understanding and AI Usage
Did you use AI assistance (ChatGPT, Claude, Copilot, etc.) to write any part of this code?
If you used AI assistance:
Explain your implementation approach:
Adds one Markdown file next to
llm_client.pyso agents/contributors know which files to touch for new HTTP LLM providers and how that differs from subprocess CLI providers.Checklist before requesting a review
Note: Please check Allow edits from maintainers if you would like us to assist in the PR.