Autonomous mode

A normal message in oluso is one agent run. Autonomous mode is the outer loop around that run. The agent plans, calls tools, reads the result, and continues on its own. Each model turn still spends the wallet. oluso scan is not part of this loop.

oluso goal

oluso goal "Add a health check and run the tests"
oluso goal "Rename the pay helper" --max-iterations 8 --max-spend 20
oluso goal "Review the auth change" --model sentinel --mode review

The argument is the goal. The command prints goal · Oluso Swift on stderr (the model name follows --model and --mode), then a progress line for every iteration. It exits when the run stops. It does not open the prompt afterwards.

/goal

Inside oluso, /goal <text> starts the same loop and then returns to the prompt. It uses 24 iterations and does not set a token cap or a spend cap. The wallet can still stop it. /goal with no text prints Usage: /goal <text>.

Progress

Each iteration prints one line. The step starts as Planning and changes when the agent calls report_step. Spent is the wallet charged in this session. Tokens are the autonomous run so far.

iteration 2/24 · Write the route · spent ₦1.20 · 340 tokens

An iteration is one agent run. Inside it the model may call tools and continue, up to 6 model turns. A normal message in the prompt, outside this loop, allows 12 model turns. Every one of those turns spends the wallet.

How it stops

A second Ctrl+C force-exits. The stalled-model reason is The model stopped using tools before the goal was met. A single chat message that stops because the wallet is empty still exits 0. Only the autonomous run uses exit 2 for the wallet.

Pause and resume

Ctrl+C aborts the current model turn, saves the session, and prints the resume command. oluso resume with no id loads the latest session for this directory. oluso resume <id> loads that session. A goal that is not met continues. A finished goal, or a chat with no goal, opens the prompt when stdin is a terminal.

oluso sessions
oluso resume
oluso resume a1b2c3d4
oluso resume a1b2c3d4 --max-iterations 24

• Resume without --max-iterations continues until the stored cap. If the run already stopped on the iteration budget, resume adds 24 iterations.
• --max-iterations N on resume allows N more iterations.
• --max-tokens and --max-spend replace the stored caps only when you pass them.
• No saved sessions. means this machine has none. No session <id>. means that id is missing.
• That session is for <cwd>. Run oluso resume <id> from that directory. means you are in a different folder.
• A terminal-less resume of a chat prints Session <id> has no paused goal. Open a terminal to continue.

Sessions are JSON files in $OLUSO_HOME/sessions, or ~/.oluso/sessions. The directory is mode 0700 and each file is mode 0600. oluso sessions lists them and does not need a sign-in. oluso resume does.

Destructive commands

The sandbox shell still refuses offensive tooling, absolute paths, and command substitution. On top of that, the session gates workspace-local destructive commands: rm -rf, git reset --hard, git clean, git checkout --, and kill. At a terminal it prints the command and Run this destructive command? [y/N]. y or yes runs it. Anything else returns The user did not approve that destructive command.

With no terminal, the same command is not run. The tool replies Destructive command refused without a person at the terminal. Pass --yes to allow workspace deletes and hard resets. This one was not run: <command>. --yes approves those workspace-local commands. It does not approve publish, force-push, sudo, chmod -R, dropping a table, or shutting the machine down. Those return Oluso refused that command. It can destroy the machine, publish a package, or force-push.

Loop tools

During oluso goal, /goal, oluso build, and oluso debug the agent also has report_step, finish, and blocked. /tools lists them under the mode's own tools. finish is refused for a build or a debug until the command rule on those pages is met. A line that is exactly GOAL_MET is accepted only when finish would have been accepted.

• Build

  oluso build scaffolds from a description and keeps going until a build or test exits 0.

• Debug

  oluso debug reproduces a failure and re-runs the anchor command until it exits 0.

• CLI reference

  Every command, the session keys, and the slash commands.