rtk-ai/rtk

feat: native rtk init for all AI agent tools (OpenClaw, NanoClaw, Aider, etc.)

Open

#825 opened on Mar 25, 2026

View on GitHub
 (4 comments) (6 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clieffort-largeenhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Context

RTK currently supports rtk init for 8 tools: Claude Code, Copilot (#823), Cursor, Gemini, Codex, Windsurf, Cline, OpenCode. Several other AI coding tools could benefit from native integration.

Proposed tools

Priority 1 (established tools)

  • Aider — popular CLI coding assistant, uses .aider.conf.yml or AIDER_* env vars
  • Continue.dev — VS Code/JetBrains extension, uses .continue/config.json
  • Zed AI — Zed editor built-in assistant, uses settings.json

Priority 2 (emerging tools)

  • OpenClaw — already has plugin in openclaw/, needs rtk init --openclaw
  • NanoClaw — similar to OpenClaw, needs investigation
  • Amp — Sourcegraph coding agent
  • Tabnine — code completion with chat
  • Codeium / Supermaven — code assistants

Priority 3 (niche/blocked)

  • Mistral Vibe — blocked on upstream BeforeToolCallback (#800)
  • KiloCode / AntiGravity — PR #802 open

Implementation pattern

Each tool follows the same pattern:

  1. Add flag to Init struct in main.rs (e.g. --openclaw, --aider)
  2. Add run_<tool>() function in init.rs
  3. Create appropriate config files (hooks, instructions, plugins)
  4. Add section in README

Current coverage

Tool Flag Status
Claude Code rtk init -g Done
Copilot rtk init --copilot PR #824
Cursor rtk init --agent cursor Done
Gemini rtk init --gemini Done
Codex rtk init --codex Done
Windsurf rtk init --agent windsurf Done
Cline rtk init --agent cline Done
OpenCode rtk init --opencode Done
OpenClaw manual plugin install TODO
NanoClaw not investigated TODO
Aider not supported TODO
Continue.dev not supported TODO
Vibe blocked upstream #800

Contributor guide

Research direction
Start by studying the existing `rtk init` implementations for tools like Claude Code (` g`), Cursor (` agent cursor`), and Gemini (` gemini`). Then replicate the pattern for each proposed tool. Begin with Priority 1 tools (Aider, Continue.dev, Zed AI). Each tool requires adding a flag to the `Init` struct in `main.rs`, a `run <tool>()` function in `init.rs`, creating config files, and updating README. Investigate configuration file formats and environment variables for each tool. For Aider, check `.aider.conf.yml` and `AIDER *` env vars. For Continue.dev, check `.continue/config.json`. For Zed AI, check `settings.json`. Then proceed to Priority 2 and 3 as needed.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70