kilocli-coding-agentRun Kilo CLI via background process for programmatic control.
Install via ClawdBot CLI:
clawdbot install codewithnathan97/kilocli-coding-agentIMPORTANT: You need to have Kilo CLI installed and configured so OpenClaw can use it without any issue.
npm install -g @kilocode/cliUse bash background mode for non-interactive coding work. For interactive coding sessions, use the tmux skill (always, except very simple one-shot prompts).
# Create temp space for chats/scratch work
SCRATCH=$(mktemp -d)
# Start agent in target directory ("little box" - only sees relevant files)
bash workdir:$SCRATCH background:true command:"<agent command>"
# Or for project work:
bash workdir:~/project/folder background:true command:"<agent command>"
# Returns sessionId for tracking
# Monitor progress
process action:log sessionId:XXX
# Check if done
process action:poll sessionId:XXX
# Send input (if agent asks a question)
process action:write sessionId:XXX data:"y"
# Kill if needed
process action:kill sessionId:XXXWhy workdir matters: Agent wakes up in a focused directory, doesn't wander off reading unrelated files (like your soul.md 😅).
bash workdir:~/project background:true command:"kilo run \"Build a snake game with dark theme\""⚠️ CRITICAL: Never review PRs in Clawdbot's own project folder!
# Option 1: Review in the actual project (if NOT clawdbot)
bash workdir:~/Projects/some-other-repo background:true command:"kilo run \"Review current branch against main branch\""
# Option 2: Clone to temp folder for safe review (REQUIRED for clawdbot PRs!)
REVIEW_DIR=$(mktemp -d)
git clone https://github.com/clawdbot/clawdbot.git $REVIEW_DIR
cd $REVIEW_DIR && gh pr checkout 130
bash workdir:$REVIEW_DIR background:true command:"kilo run \"Review current branch against main branch\""
# Clean up after: rm -rf $REVIEW_DIR
# Option 3: Use git worktree (keeps main intact)
git worktree add /tmp/pr-130-review pr-130-branch
bash workdir:/tmp/pr-130-review background:true command:"kilo run \"Review current branch against main branch\""Why? Checking out branches in the running Clawdbot repo can break the live instance!
# Fetch all PR refs first
git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'
# Deploy the army - one Kilo CLI per PR!
bash workdir:~/project background:true command:"kilo run \"Review PR #86. git diff origin/main...origin/pr/86\""
bash workdir:~/project background:true command:"kilo run \"Review PR #87. git diff origin/main...origin/pr/87\""
bash workdir:~/project background:true command:"kilo run \"Review PR #95. git diff origin/main...origin/pr/95\""
# ... repeat for all PRs
# Monitor all
process action:list
# Get results and post to GitHub
process action:log sessionId:XXX
gh pr comment <PR#> --body "<review content>"git fetch origin '+refs/pull//head:refs/remotes/origin/pr/'git diff origin/main...origin/pr/XXgh pr comment to post reviews to GitHubUse the tmux skill for interactive coding sessions (always, except very simple one-shot prompts). Prefer bash background mode for non-interactive runs.
For fixing multiple issues in parallel, use git worktrees (isolated branches) + tmux sessions:
# 1. Clone repo to temp location
cd /tmp && git clone git@github.com:user/repo.git repo-worktrees
cd repo-worktrees
# 2. Create worktrees for each issue (isolated branches!)
git worktree add -b fix/issue-78 /tmp/issue-78 main
git worktree add -b fix/issue-99 /tmp/issue-99 main
# 3. Set up tmux sessions
SOCKET="${TMPDIR:-/tmp}/kilo-fixes.sock"
tmux -S "$SOCKET" new-session -d -s fix-78
tmux -S "$SOCKET" new-session -d -s fix-99
# 4. Launch Kilo CLI in each (after npm install!)
tmux -S "$SOCKET" send-keys -t fix-78 "cd /tmp/issue-78 && npm install && kilo run 'Fix issue #78: <description>. Commit and push.'" Enter
tmux -S "$SOCKET" send-keys -t fix-99 "cd /tmp/issue-99 && npm install && kilo run 'Fix issue #99: <description>. Commit and push.'" Enter
# 5. Monitor progress
tmux -S "$SOCKET" capture-pane -p -t fix-78 -S -30
tmux -S "$SOCKET" capture-pane -p -t fix-99 -S -30
# 6. Check if done (prompt returned)
tmux -S "$SOCKET" capture-pane -p -t fix-78 -S -3 | grep -q "❯" && echo "Done!"
# 7. Create PRs after fixes
cd /tmp/issue-78 && git push -u origin fix/issue-78
gh pr create --repo user/repo --head fix/issue-78 --title "fix: ..." --body "..."
# 8. Cleanup
tmux -S "$SOCKET" kill-server
git worktree remove /tmp/issue-78
git worktree remove /tmp/issue-99Why worktrees? Each Kilo CLI works in isolated branch, no conflicts. Can run 5+ parallel fixes!
Why tmux over bash background? Kilo CLI is interactive — needs TTY for proper output. tmux provides persistent sessions with full history capture.
When submitting PRs to external repos, use this format for quality & maintainer-friendliness:
`
## Original Prompt
[Exact request/problem statement]
## What this does
[High-level description]
**Features:**
- [Key feature 1]
- [Key feature 2]
**Example usage:**command example
## Feature intent (maintainer-friendly)
[Why useful, how it fits, workflows it enables]
## Prompt history (timestamped)
- YYYY-MM-DD HH:MM UTC: [Step 1]
- YYYY-MM-DD HH:MM UTC: [Step 2]
## How I tested
**Manual verification:**
1. [Test step] - Output: `[result]`
2. [Test step] - Result: [result]
**Files tested:**
- [Detail]
- [Edge cases]
## Session logs (implementation)
- [What was researched]
- [What was discovered]
- [Time spent]
## Implementation details
**New files:**
- `path/file.ts` - [description]
**Modified files:**
- `path/file.ts` - [change]
**Technical notes:**
- [Detail 1]
- [Detail 2]
---Key principles:
Generated Mar 1, 2026
Maintainers can use this skill to automatically review pull requests in parallel, ensuring code quality without manual intervention. By fetching PR refs and running Kilo CLI in background processes, it generates reviews that can be posted directly to GitHub, saving time on large projects.
Development teams can fix multiple issues simultaneously by creating isolated git worktrees and launching Kilo CLI in tmux sessions. This allows for concurrent work on different branches without conflicts, speeding up sprint cycles and improving productivity.
Startups can leverage this skill to quickly build prototypes or MVPs by using Kilo CLI in background mode with commands like 'kilo run' for tasks such as creating a snake game. It enables rapid iteration and testing of ideas without deep coding expertise.
Enterprises can refactor legacy codebases by running multiple Kilo CLI instances in parallel to review and update code sections. Using background processes and temp directories ensures focused work without disrupting the main codebase, aiding in modernization efforts.
Educators can use this skill to set up interactive coding sessions for students via tmux, allowing real-time collaboration and guidance. By isolating work in temp directories, it provides a safe environment for learners to experiment and receive automated feedback from Kilo CLI.
Offer a subscription-based service where teams integrate this skill into their CI/CD pipelines for automated PR reviews. Revenue comes from monthly fees based on the number of repositories or review volume, targeting mid-sized software companies.
Provide consulting to help organizations implement and customize this skill for parallel coding tasks, such as bug fixing or refactoring. Revenue is generated through project-based contracts and ongoing support, focusing on enterprises with complex workflows.
Develop a free tool with basic features for individual developers and open source projects, while charging for advanced capabilities like batch PR reviews or priority support. Revenue streams include premium upgrades and sponsorships from larger tech companies.
💬 Integration Tip
Ensure Kilo CLI is installed globally via npm and use temp directories for isolation to prevent interference with live systems, especially when reviewing PRs in sensitive projects like clawdbot.
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.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
A comprehensive skill for using the Cursor CLI agent for various software engineering tasks (updated for 2026 features, includes tmux automation guide).
Write, run, and manage unit, integration, and E2E tests across TypeScript, Python, and Swift using recommended frameworks.
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.