Practical overview
When it fits
Use Yylo when a developer wants a command-line layer for organizing coding-agent work and is prepared to consult the repository for the project’s current setup and usage details.
Who it is for
- Developers using command-line coding-agent workflows.
- Teams or individuals seeking a project-level launcher for repeatable agentic development routines.
Documented uses
- Launch coding-agent workflows from a CLI.
- Create a consistent entry point for agentic software-development routines across projects.
Requirements & limits
Yylo is available through a public GitHub repository and is MIT-licensed. The available information does not specify installation requirements, pricing, account requirements, or supported operating systems.
- The tool is a CLI rather than a hosted application.
- Its implementation language is Python.
- The repository confirms equivalent
yyloandyylaunchers. - The available description does not explain the underlying orchestration mechanism or provide setup and execution instructions.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install YYLO and initialize a demo workspace
Install the YYLO CLI, initialize its workspace in a new Git repository, and inspect the workspace and command surface.
Before you start
- Node.js 20.10 or newer
- npm
- Git
Steps
Install the stable CLI: the command below.
npm install --global '@yylo/cli@latest'Check the installed version with
yy --version.Create and enter a new directory, then initialize Git:
mkdir yylo-demo && cd yylo-demo && git init.Initialize YYLO with
yy init --task "Document the onboarding path" --subagent pi.Inspect the workspace and available commands with
yy info --json,yy doctor workspace, andyy --help.
Expected outcome
YYLO initializes `.juno_task/`; the documented successful run also emits a watch receipt with state `COMPLETED`, exit code `0`, and nonzero `log_bytes`. The inspection commands show workspace information, check workspace topology, and display the command surface.
Guide limitations
- The documented canary does not contact a model provider.
- In an empty, unborn Git repository, initialization creates an initial workspace commit and a detached protected integration-owner worktree; existing or dirty repositories are not committed or rearranged by bootstrap.
doctor workspacereturns a nonzero status when it finds an actionable topology problem and does not fetch or change the workspace.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 4 October 2026
- Original website title
- yylo-dev/yylo · Official homepage title · retained in its source language

