TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/onenot8/issueLoop/llms.txt
Use this file to discover all available pages before exploring further.
issueloop CLI is the primary interface for running IssueLoop without writing Python code. It wraps the Python API into shell-friendly subcommands that map one-to-one onto the underlying library functions — so everything you can do from a Python script you can also drive entirely from a terminal, a Makefile, or a CI pipeline.
Available commands
The table below lists every subcommand and what it does at a glance. Full argument references and output examples are in the Commands page.| Command | Description |
|---|---|
check-env | Verify Ollama, models, and Supabase env are ready |
scan <repo_path> | Build a file inventory for a repo |
test <repo_name> | Run test_manifest.json commands, write log cache |
tickets <repo_name> | Create tickets from failing log entries |
next <repo_name> | Dispense the next ticket, one at a time |
watch <repo_name> | Watch a live process or log file for errors |
serve | Start the local HTTP bridge |
cleanup | Delete old done/failed tickets |
Global usage
Everyissueloop invocation accepts a --help flag. Use the top-level flag to see the list of subcommands, and the per-command flag to see that command’s arguments:
Typical workflow
The commands are designed to run in sequence. Each step feeds the next:scan writes a file inventory, test reads it and writes log output, tickets reads the logs and creates tickets, and next claims them one at a time.
Each CLI command calls the equivalent Python function directly.
issueloop scan repos/myrepo calls issueloop.scan_repo("repos/myrepo"), issueloop next myrepo calls issueloop.get_top_error("myrepo"), and so on. If you need programmatic control — looping, branching, or combining calls — switch to the Python API instead of shelling out.