Connect Factory Droid to NekoCloud
Droid BYOK reads local custom models. This guide selects OpenAI Chat Completions. In Droid, openai selects the Responses API; do not choose it solely because a model name resembles OpenAI's.1 NekoCloud has not individually acceptance-tested this toolchain and does not guarantee every model or tool call.
1. Prepare
Install and start Droid using the official Quickstart. Complete Factory's own login if prompted; a NekoCloud key is not a Factory account credential.2 Create a NekoCloud key, check balance and group permissions, and obtain the exact ID from the model plaza. Back up ~/.factory/settings.json. If customModels already exists, append one object and keep all other models and settings.
2. Minimal configuration
Set the variable in the terminal that will launch Droid:
export NEKOCLOUD_API_KEY="REPLACE_WITH_API_KEY"For a new file, use this complete JSON. Do not replace an existing file wholesale:
{
"customModels": [
{
"model": "REPLACE_WITH_MODEL_ID",
"displayName": "NekoCloud",
"baseUrl": "https://api.nekocloud.vip/v1",
"apiKey": "${NEKOCLOUD_API_KEY}",
"provider": "generic-chat-completion-api"
}
]
}| Field | Meaning |
|---|---|
customModels | Top-level custom model array |
model / displayName | API model ID / selector label |
baseUrl | Base URL; the client appends the endpoint |
apiKey | ${NEKOCLOUD_API_KEY} references the process environment |
provider | generic-chat-completion-api means Chat Completions |
The current recommended file uses camelCase. Legacy snake_case in config.json remains supported but does not have the same key environment-expansion behavior.1 Do not copy unknown maxOutputTokens values; check the model's actual capabilities before setting a limit.
3. Select and reload
Save, exit, and restart droid from the terminal with the variable. Open /model and choose NekoCloud under Custom models.1 If a separate Spec Mode model is configured, verify that it is not still routed through another provider. Appearing in the selector does not establish NekoCloud authorization.
4. Read-only verification and usage
Tests can incur charges. After confirming consent, send a greeting, enter Spec Mode with Shift+Tab, and request a README summary quoting actual text. Do not approve the transition into implementation, writes, or shell execution.3 Inspect the actual read-tool result and final answer, and confirm project files are unchanged. Compare /cost client statistics with NekoCloud usage records by time, model, and tokens; local pricing or cache displays are not the NekoCloud bill.1
Keep keys and backups out of Git. Prefer hidden input for real credentials and confirm environment inheritance after restarting. For 401, check authentication; for 404, check the model and path; for tool failures, check capabilities and protocol. Redact diagnostics and do not enable high autonomy to bypass failures.