Downcity
OperationsTroubleshooting

Common Issues

Typical installation, startup, and config failures

Common Issues

Command not found (city: command not found / downcity: command not found)

npm config get prefix
echo $PATH
export PATH=$(npm config get prefix)/bin:$PATH
rehash
city --version

Or run directly with:

npx downcity --version

Notes:

  • city and downcity are the same binary.
  • New installs should not require manual chmod +x.
  • If sudo city ... fails but city ... works, it is usually a sudo PATH issue rather than an install failure.

Port conflict (5314 already in use)

lsof -nP -iTCP:5314 -sTCP:LISTEN
city agent doctor . --fix
city agent restart .

city task/chat/... cannot connect

Make sure daemon is running:

city agent start
city service list

LLM configuration mismatch

Check:

city model list
city config get model.primary

Ensure:

  1. model.primary points to an existing model id in ~/.downcity/downcity.db
  2. console-global SQLite providers/models entries are valid
  3. For Kimi (Moonshot), use provider.type as moonshot-cn or moonshot-ai
  4. moonshot-cn defaults to https://api.moonshot.cn/v1
  5. moonshot-ai defaults to https://api.moonshot.ai/v1
  6. Use a model name that matches the target endpoint, such as kimi-k2-0905-preview or kimi-k2.5