[Assistant Rules - You MUST follow these instructions]
[Available Skills]
The following skills are available. When you need detailed instructions for a specific skill,
you can request it by outputting: [LOAD_SKILL: skill-name]
- aionui-skills: Access the AionUI Skills registry — discover and download AI agent skills. Use when you need to find a reusable skill for a task or manage your agent credentials on the AionUI Skills platform.
- cron: Scheduled task management - create, query, update scheduled tasks to automatically execute operations at specified times.
- officecli: Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
- skill-creator: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
[Skills Location]
Skills are stored in three locations:
- Builtin skills (auto-enabled): /home/ubuntu/.config/AionUi/config/builtin-skills/_builtin/{skill-name}/SKILL.md
- Bundled skills: /home/ubuntu/.config/AionUi/config/builtin-skills/{skill-name}/SKILL.md
- User custom skills: /home/ubuntu/.config/AionUi/config/skills/{skill-name}/SKILL.md
Each skill has a SKILL.md file containing detailed instructions.
To use a skill, read its SKILL.md file when needed.
For example:
- Builtin "cron" skill: /home/ubuntu/.config/AionUi/config/builtin-skills/_builtin/cron/SKILL.md
- Bundled "pptx" skill: /home/ubuntu/.config/AionUi/config/builtin-skills/pptx/SKILL.md
[User Request]
Cayou tell me if kilo code cli is installed on our VPS
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
**No, Kilo Code CLI is not installed** on the VPS. I checked everywhere — system PATH, `~/.local/bin`, npm global, pip, snap, flatpak, and filesystem — nothing with "kilo" came up.
Here's what coding CLIs **are** available:
| CLI | Path | Notes |
|-----|------|-------|
| **Claude Code** | `~/.local/bin/claude` | Also served via HTTP API on port 8643 |
| **OpenCode** | `~/.opencode/bin/opencode` | |
| **Gemini CLI** | npm global `@google/gemini-cli@0.40.1` | |
If you want Kilo Code CLI installed, I can do that — just let me know.
2026-05-08T17:18:59
USER (hermes, deepseek-v4-pro)
npm install -g @kilocode/cli see if this woks
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
Permission denied — the global npm directory requires `sudo`. Let me fix that:
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
Installed! Let me verify it works:
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
Done. **Kilo Code CLI v7.2.40** is now installed at `/usr/bin/kilo`. Ready to use.
2026-05-08T17:18:59
USER (hermes, deepseek-v4-pro)
CAN YOU TEll me how can i use it on AIonui
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
Now I have the full picture. Here's the summary:
## Kilo Code in AionUI
**Good news:** Kilo Code CLI (`kilo acp`) speaks ACP natively — the same protocol AionUI uses for Claude Code, OpenCode, etc.
**Bad news:** AionUI v1.9.20 doesn't have Kilo Code in its built-in agent detection list. But you can add it as a **Custom ACP Agent**. Here are the options:
---
### Option A: Systemd Service + Remote Agent (Recommended)
Run Kilo Code as a persistent ACP server, then connect AionUI to it:
```bash
# 1. Create a systemd service
sudo tee /etc/systemd/system/kilo-acp.service << 'EOF'
[Unit]
Description=Kilo Code ACP Server
After=network.target
[Service]
Type=simple
User=ubuntu
ExecStart=/usr/bin/kilo acp --port 9876 --hostname 127.0.0.1
Restart=on-failure
RestartSec=5
[Install]
WantedBy=multi-user.target
EOF
# 2. Enable and start
sudo systemctl daemon-reload
sudo systemctl enable --now kilo-acp
```
Then in AionUI, go to **Agents → Add Remote Agent**, point it to `http://127.0.0.1:9876`.
---
### Option B: Custom Agent (stdio, no service needed)
Add Kilo Code as a custom agent so AionUI spawns it on demand. I'd need to write the config entry to AionUI's storage. The config would be:
```json
{
"id": "kilo",
"name": "Kilo Code",
"defaultCliPath": "/usr/bin/kilo",
"acpArgs": ["acp"],
"enabled": true
}
```
---
Which approach do you prefer? **Option A** is more reliable (always running, no spawn delay). **Option B** is lighter (only runs when used).
2026-05-08T17:18:59
USER (hermes, deepseek-v4-pro)
option B to begin with
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
Config written. Now restart AionUI to pick it up:
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
The config has been updated. You'll need to restart AionUI for it to detect Kilo Code:
```bash
sudo systemctl restart aionui
```
Here's what was added to the config:
| Field | Value |
|-------|-------|
| **Agent ID** | `kilo` |
| **Name** | Kilo Code |
| **CLI Path** | `/usr/bin/kilo` |
| **ACP Args** | `acp` (subcommand, same pattern as `goose acp`, `kimi acp`) |
After restart, Kilo Code should appear in AionUI's agent list alongside Claude Code, OpenCode, Hermes, etc. Since it uses `kilo acp` over stdio, AionUI will spawn it on demand when you select it — no background service needed.
Want me to verify the config looks correct before you restart?
2026-05-08T17:18:59
USER (hermes, deepseek-v4-pro)
restart aionui
2026-05-08T17:18:59
ASSISTANT (hermes, deepseek-v4-pro)
The restart is being blocked by a safety policy on my end. You'll need to run it manually:
```bash
sudo systemctl restart aionui
```
After it restarts, Kilo Code should appear in AionUI's agent selector. Want me to verify the config is correct while you do that?