← Chat Archive

Let me check the AionUI config to see what model is set and how to update it.

This file is URL-encoded JSON. Let me decode it and search for the model setting.

It's double URL-encoded. Let me decode it properly.

So the file is base64 encoded, and inside that is URL-encoded JSON. Let me fully decode it.

Found it. The config shows `acp.cachedModels.hermes.currentModelId` is set to `deepseek:deepseek-v4-pro`, but `kimi-coding:kimi-k2.6` is available in the list. Let me also check `guid.lastSelectedAgent` to see which agent is active, and look for any other model references.

Now I understand the issue. The AionUI config has: - `guid.lastSelectedAgent`: `"hermes"` (you're using the Hermes agent) - `acp.cachedModels.hermes.currentModelId`: `"deepseek:deepseek-v4-pro"` (this is the OLD model) - `kimi-coding:kimi-k2.6` is available in the `availableModels` list The model setting is cached in `acp.cachedModels`. I need to update `acp.cachedModels.hermes.currentModelId` to `kimi-coding:kimi-k2.6` and also update `currentModelLabel`. Let me update the config file.

Config updated. Now I need to restart AionUI for the change to take effect. Let me restart the service.

AionUI restarted successfully. The service is active and running. Memory is at 258M (will grow to ~8GB as it fully loads). Summary of what I did: 1. Found the AionUI config at `/home/ubuntu/.config/AionUi/config/aionui-config.txt` 2. Decoded it (base64 -> URL-decode -> JSON) 3. Changed `acp.cachedModels.hermes.currentModelId` from `deepseek:deepseek-v4-pro` to `kimi-coding:kimi-k2.6` 4. Updated the label to `kimi-k2.6` 5. Re-encoded and wrote back 6. Restarted `aionui.service` Your AionUI session should now show **kimi-k2.6** as the active model for the Hermes agent. Give it ~10-15 seconds to fully load, then check the UI.

Goodbye. If you need anything else, just ask.