44 lines
1.2 KiB
Markdown
44 lines
1.2 KiB
Markdown
# Allegro wizard house
|
|
|
|
Purpose:
|
|
- stand up the third wizard house as a Kimi-backed coding worker
|
|
- keep Hermes as the durable harness
|
|
- treat OpenClaw as optional shell frontage, not the bones
|
|
|
|
Local proof already achieved:
|
|
|
|
```bash
|
|
HERMES_HOME=$HOME/.timmy/wizards/allegro/home \
|
|
hermes doctor
|
|
|
|
HERMES_HOME=$HOME/.timmy/wizards/allegro/home \
|
|
hermes chat -Q --provider kimi-coding -m kimi-for-coding \
|
|
-q "Reply with exactly: ALLEGRO KIMI ONLINE"
|
|
```
|
|
|
|
Observed proof:
|
|
- Kimi / Moonshot API check passed in `hermes doctor`
|
|
- chat returned exactly `ALLEGRO KIMI ONLINE`
|
|
|
|
Repo assets:
|
|
- `wizards/allegro/config.yaml`
|
|
- `wizards/allegro/hermes-allegro.service`
|
|
- `bin/deploy-allegro-house.sh`
|
|
|
|
Remote target:
|
|
- host: `167.99.126.228`
|
|
- house root: `/root/wizards/allegro`
|
|
- `HERMES_HOME`: `/root/wizards/allegro/home`
|
|
- api health: `http://127.0.0.1:8645/health`
|
|
|
|
Deploy command:
|
|
|
|
```bash
|
|
cd ~/.timmy/timmy-config
|
|
bin/deploy-allegro-house.sh root@167.99.126.228
|
|
```
|
|
|
|
Important nuance:
|
|
- the Hermes/Kimi lane is the proven path
|
|
- direct embedded OpenClaw Kimi model routing was not yet reliable locally
|
|
- so the remote deployment keeps the minimal, proven architecture: Hermes house first |