mheraskin

Soloe — Development skill for Claude Code

Development community

Local-first agent development environment for solo developers coordinating CLI agents across worktrees and devices.

How to install Soloe

This entry records only its repository, not the path inside it, so there is no exact command to give. Open mheraskin/soloe and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Soloe does

Local-first agent development environment for solo developers coordinating CLI agents across worktrees and devices.

Alternatives in Development

Claude Scholar — Semi-automated research assistant for academic research and software development 3k ★
Claude On Rails — A development framework for Ruby on Rails developers using Claude Code, inspired by SuperClaude 779 ★
Coding Agent Session Search — Unified TUI and CLI to index and search your local coding agent session history across 11+ providers (Codex, C 708 ★

README

Soloe

A local-first agent development environment for solo developers who use CLI agents.

Soloe keeps projects, worktrees, terminals, plans, and code review in one place. It runs the installed Claude Code, Codex CLI, and Cursor Agent CLI in interactive mode, with their normal authentication and terminal behavior intact.

[![CI](https://github.com/mheraskin/soloe/actions/workflows/ci.yml/badge.svg)](https://github.com/mheraskin/soloe/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)

**Public source preview.** The repository is public, but there is no binary release yet. Run Soloe from source and expect breaking changes. Soloe has no hosted cloud, analytics, or telemetry.

[Run from source](#run-from-source) · [Roadmap](./ROADMAP.md) · [Security](./SECURITY.md) · [Privacy](./PRIVACY.md) · [Contributing](./CONTRIBUTING.md)

Why I built it

I started Soloe on Windows with my development environment inside WSL. The agent tools I could find treated that setup as an edge case, and stitching together terminals, worktrees, plans, and review took more effort than the work itself.

My normal setup has a few long-running feature worktrees. Each may have Claude Code, Codex, or Cursor running in a real terminal. I want to see what is active, return to a session days later, review the feature across its full commit history, and send a precise comment back to the agent. Soloe grew around that loop.

Soloe is named for this way of working. Agents help me take on more, but I still decide what to build and what is safe to ship.

What works today

Interactive CLI agents. Soloe runs installed claude, codex, and Cursor agent binaries on macOS, Linux, native Windows, or inside WSL.
Project and worktree organization. Sessions stay attached to the checkout where their work belongs. A logical workspace can have independent checkouts on more tha