ropeshift

A free, fair-source, self-hosted software factory for people who run coding agents in parallel.

Alpha, v0.1.0-alpha.14 (opens in a new tab)

Solo mode works on macOS and Linux. Expect breaking changes before 1.0.0.

It turns planned work into verified outcomes with supervised agents, and it is designed to interrupt a person only when a person is needed. This release drives Claude Code on one machine.

Install with Homebrew
brew install bkuberek/tap/ropeshift

Or use the install script, or a .deb or .rpm package.

The problem

  • Starting several agent sessions is easy. Keeping them productive for hours is not.
  • Two sessions can take the same work, and nobody notices until a branch is damaged.
  • Agents stop to ask questions, often the same ones, and sessions sit idle waiting for a person.
  • Agents do not share one view of the goals, requirements, and past decisions.
  • There is no single place to see what is planned, running, stuck, or finished.

How work flows

In this release, work moves through these seven steps on one machine.

Rope yards laid one colored yarn into a rope to mark it. Here that yarn is you, and it touches the lane only at the last rung.

See the diagrams

Few interruptions
The north-star metric is human interruptions per completed work order, and ropeshift measures prints it beside the measures that keep it honest.
Never ask twice
Lanes with the same open question attach to it, and every one of them hears the one answer.
No assumed roles
Every member can answer any question and make any decision.
  1. Work arrives from repository files or directly in the ledger.Designed, not built yet: reading it from a tracker
  2. A person or a planning agent writes a plan and its contracts.
  3. Contract review collects every question it can find, in one batch. Work becomes ready only when it passes a definition of ready.
  4. An orchestrator claims ready work and starts a lane: one writer in one worktree.
  5. When a lane has a question, it climbs a ladder, and a person is the last rung.
    1. Existing decisions
    2. Open questions
    3. A decision within policy
    4. A recorded assumption
    5. A person
  6. A lane that truly cannot proceed parks. It saves its work, stops its process so it uses no quota, and resumes when the answer arrives.
  7. The lane ends with a typed outcome, artifacts, and check results, and a member accepts the work or sends it back for rework.Designed, not built yet: writing the result back to a tracker

The four parts

Each part is built for solo mode in this release.

The rope reads left to right: loose yarns, then laid rope. This page marks each part the same way.

Built in v0.1.0-alpha.14
Laid: twisted and finished. It works in this release.
Designed, not built yet
Loose: not spun in yet. It is part of the design.
  • Built in v0.1.0-alpha.14

    Work ledger

    The system of record for execution, in a local SQLite ledger per project.

    • Claims, outcomes, decisions, and evidence
    • Many isolated projects per installation
    • No tracker required
  • Built in v0.1.0-alpha.14

    Planning and decisions

    A planning session turns your answers into requirements, documents, milestones, contracts, and work orders, approved as one plan.

    • Adopt an existing project
    • Contract review before work starts
    • Every decision searchable, with its rationale
  • Built in v0.1.0-alpha.14

    Supervised agents

    One orchestrator per machine pulls work, and a deterministic daemon keeps each Claude Code session healthy.

    • A lost claim stops its writer
    • A verdict on every review criterion
    • Merges at the authority level you choose
  • Built in v0.1.0-alpha.14

    Web UI

    The web UI shows every project in the installation, on loopback, with ropeshift top beside it in a terminal.

    • Needs you, with confirmation cards
    • Roadmap, plans, and plan approval
    • Lanes, measures, and conversations

Designed, not built yet: reading work from an issue tracker and writing results back to it, workers on more than one machine, and drivers for Codex and opencode

See it

The web UI is built into the binary, and its first view puts what waits for a person first.

Take the tour

The Needs you view of the ropeshift web UI, with nine items waiting in two projects, oldest first. The list includes work to accept, a blocked work order, a parked lane, a tool call, questions, two confirmation cards, a plan approval, and a contract review. The first, Retry idempotent requests with backoff, is open, with the review's Pass for two criteria and the buttons Send back for rework and Accept.
The Needs you view. Captured from ropeshift v0.1.0-alpha.14 with sample data.

Works with your tools

Your tools stay. No particular tracker or process is required, and ropeshift works with no tracker at all. It wraps agent CLIs and never replaces them, and it is not a model client.

What ropeshift works with, built and designed
Built in v0.1.0-alpha.14Designed, not built yet
AgentsClaude Code, qualified on 2.1.316, 2.1.317, and 2.1.319Codex, opencode, and other agent CLIs
WorkRepository files, and work recorded directly in the ledgerGitHub Issues and Projects, Jira, Linear, Notion, YouTrack, and Odoo Projects, with results written back
KnowledgeDocuments in your repositoriesConfluence and Notion
CodeGit repositories on this machine, with one worktree per lane, and GitHub pull requests through the gh CLI you signed in to, or merging into the base branch with gitBitbucket pull requests

Ways to run it

Team size changes configuration, not concepts, and every mode is designed to use the same versioned API.

  • Built in v0.1.0-alpha.14

    Solo

    One binary on one machine, with no Docker, no account, and no network connection of its own.

    Store: SQLite

  • Designed, not built yet

    Self-hosted group

    Docker Compose on a LAN or tailnet, with workers that dial out, so laptops open no inbound ports.

    Store: Postgres

  • Designed, not built yet

    Cluster

    A Helm chart and Terraform modules in your own cloud.

    Store: Postgres

Your logins stay yours

Each agent CLI is installed and signed in on each worker, through its vendor's own flow. Ropeshift never reads, stores, relays, or proxies agent credentials.

A worker that uses a subscription is bound to the person who signed in, and shared workers use API keys.

Install the alpha

Install with Homebrew
brew install bkuberek/tap/ropeshift
Or with the install script
curl -fsSL https://raw.githubusercontent.com/bkuberek/ropeshift/main/install.sh | sh

Ropeshift is free and fair source under the Functional Source License, FSL-1.1-ALv2. Each version also becomes available under Apache-2.0 two years after its release. Outside code contributions are not open yet.

Support ropeshift

Ropeshift is free to use. If it helps your work, you can support its development with a one-time contribution or a monthly sponsorship.

Why and how to support