Skip to content
Oluso

Get started

Debug

oluso debug reproduces a failure, reads the output, applies a fix, and re-runs until the failure is gone.

On this page

oluso debug is an autonomous run anchored on a failing command or test. It uses the same loop, sandbox, wallet, and budgets as Autonomous mode.

Command

bash

oluso debug --command "pnpm test"
oluso debug "checkout throws when the cart is empty" --command "pnpm test"
oluso debug "The login request returns 500"

oluso debug

  • descriptionstringoptional

    What is failing. Optional when --command is set.

  • --commandstringoptional

    The command or test to reproduce and re-run. finish is accepted only after this exact string exits 0.

With neither a description nor --command, the command prints Debug needs a description or --command. and exits 1. The other flags match oluso goal, including --max-iterations default 24. Stderr starts with debug · Oluso Swift unless you changed the model.

The loop

  1. Run the anchor command, or find a failing command when you did not pass --command.
  2. Read the stack trace and the logs.
  3. Call report_step with one hypothesis.
  4. Edit the code.
  5. Re-run the same command.
  6. Call finish only when that command exits 0.

When it may finish

  • With --command, finish waits until that exact command has exited 0. The refusal is Finish is waiting on the anchor command. Run it and get exit 0: <command>.
  • Without --command, finish waits until bash has run at least once. The refusal is Finish is waiting on a reproduction. Run the failing command with bash first.
  • A passing run prints Debug met on iteration N. <summary> and exits 0.

Ctrl+C pauses and saves. Continue with oluso resume <id> from the same directory. Budgets, the wallet, and the destructive-command gate are the ones on the Autonomous mode page.