Skip to content

Detailed updates to the KiloClaw docs#6366

Open
olearycrew wants to merge 3 commits intomainfrom
docs/update-kiloclaw-docs
Open

Detailed updates to the KiloClaw docs#6366
olearycrew wants to merge 3 commits intomainfrom
docs/update-kiloclaw-docs

Conversation

@olearycrew
Copy link
Contributor

Context

this provides a much more comprehensive overview of Kilo Claw and the current state of how it works so that users can understand more of the technical details about the instances that are running on and how that interacts with OpenClaw.

CleanShot 2026-02-25 at 15 31 03

That is accomplished through starting to break the Kilo Claw documentation into a number of pages:

  • Overview,
  • Dashboard (our KiloClaw dashboard)
  • Control UI (the OpenClaw control UI)
  • Chat platforms (Telegram, Discord, etc.)
  • Troubleshooting
  • Pricing

@kilo-code-bot
Copy link
Contributor

kilo-code-bot bot commented Feb 25, 2026

Code Review Summary

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 2
SUGGESTION 0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

CRITICAL

File Line Issue
None - -

WARNING

File Line Issue
packages/kilo-docs/pages/automate/kiloclaw/chat-platforms.md 26 Use markdown image syntax in markdown docs
packages/kilo-docs/pages/automate/kiloclaw/chat-platforms.md 37 Use markdown image syntax in markdown docs

SUGGESTION

File Line Issue
None - -
Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

File Line Issue
None - -
Files Reviewed (12 files)
  • packages/kilo-docs/lib/nav/automate.ts - 0 issues
  • packages/kilo-docs/pages/automate/kiloclaw/chat-platforms.md - 2 issues
  • packages/kilo-docs/pages/automate/kiloclaw/control-ui.md - 0 issues
  • packages/kilo-docs/pages/automate/kiloclaw/dashboard.md - 0 issues (existing inline warning already present on line 10)
  • packages/kilo-docs/pages/automate/kiloclaw/overview.md - 0 issues (existing inline warning already present on line 36)
  • packages/kilo-docs/pages/automate/kiloclaw/pricing.md - 0 issues
  • packages/kilo-docs/pages/automate/kiloclaw/troubleshooting.md - 0 issues
  • packages/kilo-docs/previous-docs-redirects.js - 0 issues
  • packages/kilo-docs/public/img/kiloclaw/dashboard.png - binary asset reviewed
  • packages/kilo-docs/public/img/kiloclaw/discord.png - binary asset reviewed
  • packages/kilo-docs/public/img/kiloclaw/slack.png - binary asset reviewed
  • packages/kilo-docs/public/img/kiloclaw/telegram.png - binary asset reviewed

Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
@vercel
Copy link

vercel bot commented Feb 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs (docs-staging) Ready Ready Preview, Comment Feb 25, 2026 8:38pm

Request Review

Copy link
Contributor

@pandemicsyn pandemicsyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, mostly small nit picky stuff you can ignore. Only thing we really need to update is the instance info.

6. Click **Create & Provision**

Your instance will be provisioned and ready within seconds.
Your instance will be provisioned in seconds. Each instance runs on a dedicated machine with 2 shared vCPUs, 4 GB RAM, and a 20 GB persistent SSD. Once created in a region, your instance always runs there.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Your instance will be provisioned in seconds. Each instance runs on a dedicated machine with 2 shared vCPUs, 4 GB RAM, and a 20 GB persistent SSD. Once created in a region, your instance always runs there.
Your instance will be provisioned in seconds. Each instance runs on a dedicated machine with 2 shared vCPUs, 3 GB RAM, and a 10 GB persistent SSD. Once created in a region, your instance always runs there.

- **Restart** — Stop and start the instance
- **Start Machine** — Boot a stopped instance (up to 60 seconds)
- **Restart OpenClaw** — Quick restart of just the OpenClaw process; the machine stays up
- **Redeploy** — Update and restart the whole machine; all your files and data are preserved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Redeploy**Update and restart the whole machine; all your files and data are preserved
- **Redeploy**This will stop the machine, apply any pending image or config updates, and restart it. The machine will be briefly offline.

- **Redeploy suggested** — Redeploy is optional and only needed if you want to use the new behavior

For example, if you manually configured a channel such as Telegram, and would prefer to have KiloClaw manage the channel for you, you would need to redeploy.
When someone messages your bot for the first time, or a new device connects to the Control UI, you'll see a pairing request on the dashboard that you need to approve. See [Pairing Requests](/docs/automate/kiloclaw/chat-platforms#pairing-requests) for details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When someone messages your bot for the first time, or a new device connects to the Control UI, you'll see a pairing request on the dashboard that you need to approve. See [Pairing Requests](/docs/automate/kiloclaw/chat-platforms#pairing-requests) for details.
When you initialize a new channel for the first time, or a new device connects to the Control UI, you'll see a pairing request on the dashboard that you need to approve. See [Pairing Requests](/docs/automate/kiloclaw/chat-platforms#pairing-requests) for details.

Not sure that its always message driven so hedging bets a bit.


### When should I use Restart OpenClaw vs Redeploy?

- **Restart OpenClaw** — Restarts just the OpenClaw process. The machine stays up. Use this for quick recovery from a process-level issue.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Restart OpenClaw** — Restarts just the OpenClaw process. The machine stays up. Use this for quick recovery from a process-level issue.
- **Restart OpenClaw** — Restarts just the OpenClaw process. The machine stays up. Use this for quick recovery from a process-level issue or when you want to apply openclaw config changes.

Comment on lines +48 to +50
### I changed the model but the agent is still using the old one

After selecting a new model, click **Save & Provision** to apply it. This refreshes the API key and saves the new model. You may also need to **Restart OpenClaw** for the change to take full effect.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't have to change this now. But was also chatting with John today - when we native gateway we should probably just default to auto or something and push users towards the OpenClaw Control UI to change model defaults and the like. Because chances are thats where most folks will go to manage model+agent pairings and the like anyway.

Comment on lines +76 to +78
### Safe Bins

A small set of stdin-only binaries (`jq`, `cut`, `uniq`, `head`, `tail`, `tr`, `wc`) are allowed in `allowlist` mode without explicit entries. These enforce strict stdin-only behavior — positional file arguments, path-like tokens, shell expansion, and redirections are all rejected.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Safe Bins
A small set of stdin-only binaries (`jq`, `cut`, `uniq`, `head`, `tail`, `tr`, `wc`) are allowed in `allowlist` mode without explicit entries. These enforce strict stdin-only behavior — positional file arguments, path-like tokens, shell expansion, and redirections are all rejected.

I actually still get prompted for these the first time, so might be worth just ommiting this for now until we can poke at it some more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants