---
description: Common high-frequency YutoCode commands for conversation, updates, status checks, open, up, and extended capabilities.
---

# Common Commands

This page only covers the most useful command set for normal users. The goal is operational fluency, not memorizing every command surface at once.

## Basic Commands

```bash
yuto --help
yuto --version
yuto doctor --json
yuto auth status --json
yuto
yuto --print "Explain this repository."
```

A useful way to think about them:

- `yuto`: enter a persistent conversation
- `yuto --print ...`: run once, get the result, and exit
- `yuto doctor --json`: inspect environment and diagnostics
- `yuto auth status --json`: inspect the current auth state

## Update and Rollback

```bash
yuto update
yuto update --check
yuto update <version>
yuto rollback --list
yuto rollback --dry-run
```

The safest order is to check first, update after confirmation, and only inspect rollback when a version behaves unexpectedly.

## Open Files and Links

```bash
yuto open README.md
yuto open https://example.com
```

These commands are useful when you want to open a local file or a URL quickly during a session without switching applications manually.

## Restore Context from Project Guidance

```bash
yuto up
```

It tries to read the nearest `YUTO.md`, `CLAUDE.md`, or `.claude/CLAUDE.md` and recover the project conventions from there.
This is useful when you enter an unfamiliar codebase or want to restore context quickly.

## Commands Related to Browser or Remote Capabilities

```bash
yuto chrome status --json
yuto chrome browsers --json
yuto chrome open https://example.com --print --json
yuto ssh status --json
yuto ssh hosts --json
```

Do not turn everything on at once. A better strategy is:

- use `chrome` when you actually need browser interaction
- use `ssh` when you actually need remote connectivity

## Common Slash Commands in a Session

- `/help`
- `/login`
- `/status`
- `/provider`
- `/model`
- `/tools`
- `/approval`
- `/config`
- `/clear`
- `/exit`

## A Minimal Daily Flow

If you use YutoCode every day, start from this compact flow:

1. `yuto auth status --json`
2. `yuto`
3. describe the task in the session and let it analyze before executing
4. check `yuto update --check` when you want to see whether a new public release exists

Getting this loop smooth matters more than memorizing many commands on day one.