Guides

Updates & Troubleshooting

Update YeePilot safely, understand release channels, and troubleshoot provider, auth, vault, and sandbox issues.

Last updated: May 15, 2026

Check Your Current Build

Before troubleshooting an update problem, confirm what you are running:

bash

yeepilot version
yeepilot status

Normal Update Commands

Check without installing:

bash

yeepilot update --check

Install the newest available build for your channel:

bash

yeepilot update

Force a reinstall:

bash

yeepilot update --force

Roll back to the previously installed binary:

bash

yeepilot update --rollback

Update Channels

YeePilot supports:

public
canary

Config example:

yaml

update:
  auto_check: true
  check_interval_hours: 1
  channel: public
  channel_token: ""

Protected canary usage typically needs both:

update.channel: canary
update.channel_token: <token>

The same settings can also be supplied with environment variables:

YEEPILOT_UPDATE_CHANNEL
YEEPILOT_UPDATE_CHANNEL_TOKEN

Automatic Update Checks

Enable or disable startup checks:

yaml

update:
  auto_check: true
  check_interval_hours: 1

Use a larger interval if you prefer fewer checks.

Diagnostics And Support Commands

YeePilot includes end-user diagnostics helpers:

bash

yeepilot diagnostics pending
yeepilot diagnostics report-last

You can also send a manual redacted support report:

bash

yeepilot support report --message "Describe the issue"

Useful flags include:

--title
--context
--severity
--include-debug-log

Common Problems

Provider or model errors

Check:

the provider is correct
the model belongs to that provider
the API key is valid
your account actually has access to the chosen model

Quick one-shot test:

bash

yeepilot exec --provider openai --model gpt-4o "health check"

Platform auth or device access issues

Re-run auth management:

bash

yeepilot setup --auth

Then check again with:

bash

yeepilot status

Sandbox issues

Check the current state in-session:

text

/sandbox status

If the task truly needs network, namespaces disabled, or higher limits, change only the smallest setting required.

Vault issues

Check vault status:

bash

yeepilot vault status

Verify unlock:

bash

yeepilot vault unlock --method password

Rotate recovery when needed:

bash

yeepilot vault rotate-recovery --unlock-method password

Config drift

If your config is badly out of shape:

bash

yeepilot setup --reset

This regenerates the main config and walks you through setup again.

A Good Recovery Order

When YeePilot feels broken, work in this order:

yeepilot version
yeepilot status
yeepilot setup --auth
verify provider and model settings
run a simple yeepilot exec test
inspect diagnostics and send a support report if needed

This usually separates update problems from auth problems, provider problems, and local config problems very quickly.

Best Practices

Guides