Maintenance and troubleshooting
This page gathers the commands that **aren't part of daily development but come in handy now and then **: upgrading the CLI, reviewing command history, installing Agent Skills, and migrating from old scaffolding.
Upgrading the CLI itself
rabetbase updateOr check the help first to confirm the current behavior. After upgrading, run rabetbase doctor again to confirm PATH and local caches point to the new version.
Diagnosing environment and login: doctor
rabetbase doctorIt checks configuration, login state, connectivity, and more (the actual output is authoritative). **When login or network issues appear, run this first ** — it pinpoints problems much faster than repeatedly retrying api pull.
Command history: logs
The CLI records the commands you've run, so you can recall "what exactly did I just type":
rabetbase logs showPlain rabetbase logs is equivalent to show.
Clear it:
rabetbase logs clearWhether sensitive details end up in logs depends on the CLI version — don't treat log files as confidential storage. Keep important tokens in environment variables or a secrets manager.
Installing developer Skills: skill install
To use the official curated Lovrabet Skill package in your AI editor:
rabetbase skill installIt goes through an npx skills-style flow where you pick the IDE interactively. The old alias rabetbase skills is deprecated — use the command above.
Migrating from lovrabet-cli to rabetbase-cli: project upgrade
If an older project still carries legacy config, Skills, or MCP entries:
rabetbase project upgradeIt **analyzes ** first, then asks whether to proceed; fully automatic:
rabetbase project upgrade --yesCommit or back up the repository before migrating. The upgrade handles config file renames, removes obsolete MCP configuration, and more — see the interactive prompts and command docs for details.
Where to look for common problems
| Symptom | Suggestion |
|---|---|
| Not-logged-in / 401 errors | See the Rabetbase CLI 2.0 quick start guide, then run auth login again |
| Wrong data, looks like the wrong database | See Configuration: apps, environments, multi-app and double-check appcode, env, --app |
| Scripts won't run | See Daily development: running scripts and local debugging, then use rabetbase run |
| Can't remember flags or env vars | See the Rabetbase command reference |
Recap
update: upgrade the CLI.doctor: diagnose environment, configuration, and login state.logs: see what you typed.skill install: install AI Skills.project upgrade: migration for long-time users.
Back to the tutorial landing page: Rabetbase CLI 2.0 🔥.