Show HN: Rove – parallel coding agents that can fan out subtasks and report back Rove, a terminal-native workspace for running multiple coding tasks in parallel with Claude Code, Codex, Copilot, Kimi, or any registered CLI, has been released. It isolates parallel work in git worktrees and branches, keeps agent and shell sessions running when disconnected, and supports macOS, Linux, and Windows. Rove can be installed via a one-line script, npm, bun, or npx, and includes an API for automation. Rove is a terminal-native workspace for running multiple coding tasks in parallel with Claude Code https://claude.com/claude-code , Codex https://github.com/openai/codex , Copilot https://github.com/github/copilot-cli , Kimi, or any CLI you register. Rove isolates parallel work in git worktrees and branches, while agent and shell sessions keep running when you disconnect. Documentation https://docs.rove.sma1lboy.me · Quick start https://docs.rove.sma1lboy.me/docs/quick-start · Concepts https://docs.rove.sma1lboy.me/docs/concepts · CLI https://docs.rove.sma1lboy.me/docs/cli · Agent API https://docs.rove.sma1lboy.me/docs/api · Website https://rove.sma1lboy.me The sidebar tracks tasks and their sessions, the workspace embeds the active agent or shell, and the files pane shows the worktree's changes. Switch tasks to review output, inspect diffs, run tests, or send the next instruction. One line, on a machine with nothing installed — it sets up the Bun runtime Rove needs, then Rove itself: curl -fsSL https://rove.sma1lboy.me/install.sh | sh Or use the package manager you already have: npm install -g @sma1lboy/rove offers to install Bun on first launch bun install -g @sma1lboy/rove if you already run Bun npx @sma1lboy/rove try it without installing Install the skill to let a coding agent orchestrate Rove directly: rove skill install Then launch it in a repository: cd your-repo rove Rove needs git and at least one supported agent CLI on PATH , and runs on macOS, Linux, and Windows; Windows also requires Node.js and Git for Windows/Git Bash. The CLI itself runs on Bun https://bun.sh ≥ 1.3.11 — every install route above brings it along, and ROVE BUN=/path/to/bun points Rove at a Bun installed somewhere unusual. Press n , choose a repository, base branch, and agent, then enter a prompt. Press F1 for the live keybinding reference; ctrl+q returns to the sidebar and quits from there without stopping sessions. The package also installs kobe as a compatibility alias; rove is the canonical command. On first launch, supported legacy state is copied additively into ~/.rove ; existing files and worktrees stay in place. Parallel tasks — keep a refactor, bug fix, test investigation, and review moving at the same time. Git isolation — each managed task owns a worktree and branch, so agents working on different tasks do not overwrite each other's files. Persistent sessions — quit the TUI or drop SSH, then reattach without stopping the work. Your existing agents — use the real Claude Code, Codex, Copilot, Kimi, or custom CLI, with its own authentication, permissions, models, and access to the local environment. Terminal-native — run Rove where the code lives: laptop, devbox, VPS, or a narrow mobile SSH session. Automation-ready — scripts and coding agents can create, inspect, message, and land tasks through rove api . Managed task ├── git worktree ├── git branch └── terminal tabs ├── Claude Code ├── Codex └── shell Tabs inside one task share its files; create separate managed tasks when work needs isolation. Project-main tasks and rove . directory tasks deliberately reuse an existing directory. Sessions continue in the background when the TUI detaches, and Rove restores them when you return. The usual loop is simple: start several different tasks, switch between their live sessions, review each worktree's diff and checks, send follow-up instructions, then merge the completed branches. See Concepts /Sma1lboy/rove/blob/main/docs/CONCEPTS.md and Sessions /Sma1lboy/rove/blob/main/docs/SESSIONS.md for the full lifecycle. rove api exposes the same task model to shell scripts and coding agents. A typical workflow creates a task, checks its output, sends follow-up instructions, and lands the completed branch: rove api add --repo "$PWD" --prompt "Fix the flaky auth test." rove api list rove api read-output --task-id