OperationsTroubleshooting
Common Issues
Typical installation, startup, and config failures
Common Issues
Command not found (studio: command not found / studio: command not found)
npm config get prefix
echo $PATH
export PATH=$(npm config get prefix)/bin:$PATH
rehash
studio --versionOr run directly with:
studio --versionNotes:
studioandcitycome from the samedowncitypackage but expose different command surfaces.- New installs should not require manual
chmod +x. - If
sudo studio ...fails butstudio ...works, it is usually asudoPATH issue rather than an install failure.
Port conflict (5314 already in use)
lsof -nP -iTCP:5314 -sTCP:LISTEN
studio agent doctor . --fix
studio agent restart .studio task/chat/... cannot connect
Make sure daemon is running:
studio agent start
studio plugin listLLM configuration mismatch
Check:
studio model list
studio config get model.primaryEnsure:
model.primarypoints to an existing model id in~/.downcity/downcity.db- console-global SQLite providers/models entries are valid
- For Kimi (Moonshot), use
provider.typeasmoonshot-cnormoonshot-ai moonshot-cndefaults tohttps://api.moonshot.cn/v1moonshot-aidefaults tohttps://api.moonshot.ai/v1- Use a model name that matches the target endpoint, such as
kimi-k2-0905-previeworkimi-k2.5