Agent Hub Get started ↗

Restore agent settings

Review the way back before changing your setup.

Trying a shared Hub should come with a clear recovery path. Hub records managed originals and write history, then checks current files before undoing changes. Choose the recovery scope that matches what you want to reverse.

Recovery depends on saved originals. Multi-file rollback is compensating, not power-loss-safe.

Agent Hub resource inventory with fictional projects and resources
Real Hub interface with fictional data. The guide explains the workflow and its limits.

Pick the right recovery scope.

Inspect, preserve, then confirm.

  1. Keep recovery storage

    Retain the private sibling recovery directory. It contains originals, write records and archives needed for guarded recovery and may contain credentials.

  2. Review the scope and current files

    Choose undo, restore or reset and read the preview. Later edits, invalid ownership or missing baseline data can block an unsafe rollback.

  3. Apply and check native clients

    Use the fresh reviewed confirmation or emitted command. Inspect the outcome and restart affected clients. Keep archived current data until you are satisfied.

Before you start

Does uninstalling the CLI restore client settings?

No. Uninstall removes the package binaries. It does not automatically restore native configurations, remove every launcher or delete the saved archive.

Does reset erase all work since setup?

Reset archives current managed state before restoration, but its scope can include the whole Hub. Read the complete plan and preserve recovery storage; a missing baseline cannot be recreated as the original.

Preview the way back while the setup is still small.

The recovery guide covers later edits, interrupted writes, baseline scopes, archives and the difference between restore and uninstall.

See the steps ↗
Usage statistics

On by default. We use PostHog through our relay to count page visits and actions such as opening setup instructions or copying the install command. A random browser ID is stored locally. No cookies, session replay, full referrer URLs or page queries are sent. This setting is separate from analytics in the local app.