-
Notifications
You must be signed in to change notification settings - Fork 2.5k
docs(kiloclaw): update pricing FAQ and add recover-with-kilo guide #10070
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
LigiaZ
wants to merge
4
commits into
main
Choose a base branch
from
docs-deflecting-updates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+85
−3
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
b14d74a
docs(kiloclaw): update pricing FAQ and add recover-with-kilo guide
f401cc3
docs(kiloclaw): update usage instructions for recover-with-kilo
bd5dd0a
docs(kiloclaw): complete recover-with-kilo usage guide
4452ab1
docs(kiloclaw): add recover-with-kilo to navigation
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
53 changes: 53 additions & 0 deletions
53
packages/kilo-docs/pages/kiloclaw/control-ui/recover-with-kilo.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| --- | ||
| title: "Recover with Kilo" | ||
| description: "How to use Recover with Kilo to fix KiloClaw instances" | ||
| --- | ||
|
|
||
| # Recover with Kilo | ||
|
|
||
| ## What is Recover with Kilo? | ||
|
|
||
| Recover with Kilo is a self-repair capability built into KiloClaw. When your instance has configuration issues, broken integrations, or other operational problems, you can launch a Kilo CLI Run — an AI-powered repair agent that diagnoses and fixes the issue directly on your KiloClaw machine, without needing to contact support. | ||
|
|
||
| Think of it as an automated sysadmin that runs inside your instance. You describe the problem in plain English, and the agent investigates, identifies the root cause, and applies fixes. | ||
|
|
||
| ## When to Use It | ||
|
|
||
| Use Recover with Kilo when your KiloClaw instance is behaving unexpectedly, for example: | ||
|
|
||
| - A channel (Slack, Discord, Telegram) stopped working | ||
| - Gateway connections failing or timing out | ||
| - Model provider errors or configuration issues | ||
| - Missing or corrupted OpenClaw config | ||
| - Environment variables not propagating correctly | ||
| - Integration setup problems (GitHub, Linear, etc.) | ||
| - The instance is running but something isn't working as expected | ||
|
|
||
|
|
||
| ## How to Use It | ||
|
|
||
| 1. Go to the [KiloClaw dashboard](https://app.kiloclaw.com) | ||
| 2. Click on the "Recover with Kilo" button in the top right corner | ||
| 3. Describe the problem you're experiencing in plain English | ||
| 4. Click "Run" to launch the repair agent | ||
| 5. Wait for the agent to complete its investigation and apply fixes | ||
| 6. Refresh your browser to see the changes | ||
|
|
||
| ## Limitations | ||
|
|
||
| - Recover with Kilo can only fix issues that are within its scope of knowledge | ||
| - It cannot access or modify files outside of the KiloClaw instance | ||
| - Some complex issues may require manual intervention | ||
| - The agent may not be able to fix issues that require human judgment | ||
|
|
||
| ## Troubleshooting | ||
|
|
||
| If Recover with Kilo doesn't resolve your issue: | ||
|
|
||
| 1. Try describing the problem in more detail | ||
| 2. Check the logs for any error messages | ||
| 3. Contact support for manual assistance | ||
|
|
||
| ## Feedback | ||
|
|
||
| We're constantly improving Recover with Kilo. If you have suggestions or encounter issues, please let us know through the in-app feedback system. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.