Products Sproutle

Sproutle

A Windows workspace and orchestration layer for AI coding command-line tools. It doesn't replace Claude Code, Codex or Copilot CLI. It organizes them and runs them together.

Available soon· status as of September 2026

Sproutle's mascot: a small green turtle with a seedling on its head, peeking out of a shell with a terminal prompt on it.
sproutle workspace create demo --path C:\work\demo
workspace demo ready
sproutle -w demo pipeline run quickflow
plan     claude    done
review   approval gate: waiting for you
sproutle -w demo pipeline approve <run-id> review
build    codex     running
Commands from the Sproutle CLI; output shortened.

What's in the box

Point it at Claude Code, OpenAI Codex, GitHub Copilot CLI, or any other installed CLI through the generic adapter. Your project setup stays as plain JSON and Markdown on disk.

  • .sproutle/

    Workspaces

    Portable project environments stored as plain files in the project, friendly to source control.

  • agents/*.md

    Agents, skills, prompts

    Reusable per project or globally. A project's version overrides the global one.

  • pipeline run

    Pipelines

    Multi-agent workflows that hand work from one stage to the next, with approval gates by default.

  • creation · working

    Assistant

    Creation mode drafts project resources and shows a diff, writing only after you approve. Working mode is a real embedded terminal.

  • launcher generate

    Launchers

    Branded Windows entry points that open straight into a workspace. (This is the former CLI Launcher Generator, now part of Sproutle.)

  • sproutle.exe

    CLI

    The same operations from a script: workspaces, launchers, pipelines, resources and sessions.

Pipelines stop and ask

A pipeline hands work from one AI session to the next. By default a person approves each hand-off before the next stage starts.

  1. Stage 1Agentplans the change
  2. GateYouapprove or stop
  3. Stage 2Agentdoes the work

Honest permissions

You declare what each stage may do: read, write, execute, network. Where a CLI has a real control for that, Sproutle sets it. Where it doesn't, Sproutle says so. It labels the permission declared, not enforced instead of pretending there's a safety boundary that isn't there.

Bypass flags are never passed unless you turn on an unsafe mode yourself.

How declared permissions are applied for each CLI
CLIDeclared permissions becomeResult
Claude Code--allowedTools--permission-modeEnforced
OpenAI Codex--sandboxEnforced
GitHub Copilot CLI--allow-toolEnforced
Any other CLIno control Sproutle can setDeclared, not enforced

Sproutle or Dugout?

Sproutle runs the work: pipelines, terminal sessions, launchers.

Dugout keeps your setup and context consistent: configuration and memory across tools, checkpoints, handoffs. See Dugout

Available soon

Sproutle is open source (MIT) and built with Tauri 2, Rust and React. The first public release is being prepared. Want to hear when it's out, or try it early?

Email Buck about Sproutlebuck@bucksandco.co