Personal Agentic OSFIELD GUIDE / WIKIفارسی ↗
Learning path

STEP 6 OF 6

Verify installation and run the first sync

Check connections, the proposed project map, and sync results before relying on the Dashboard.

Last reviewed:

Search runs on this device.

On this page

Overview

The wizard shows proposed projects and connections and asks approval before writing memory. Projects merge only through an exact path, repository identity, or strong content markers; name similarity alone is insufficient. After sync, review created, updated, unchanged, and removed states.

Run the first sync

In these commands, /absolute/path/to/config.json is a placeholder: replace it with your generated configuration file. After approving the map, run npx personal-agentic-os@latest sync /absolute/path/to/config.json. Compare created, updated, unchanged, and removed states with expected changes.

Verify without changing data

Run npx personal-agentic-os@latest verify /absolute/path/to/config.json to inspect memory evidence and sync integrity without changing project data. Then run npx personal-agentic-os@latest dashboard /absolute/path/to/config.json and review context-pack coverage and records needing review.

Troubleshooting and updates

If data is missing, check the configuration path, selected sources, and connection result first; do not interpret missing values as zero. Check release status with npx personal-agentic-os@latest update /absolute/path/to/config.json. A required update can pause sync in supported versions but never changes files automatically.

Continue safely

Recurring sync is enabled only with your approval. Optimization recommendations are advisory: Preview makes no changes, Apply requires approval and a local audit, and Rollback refuses to overwrite newer user edits. Review the proposal and target paths before applying changes.

Completion checklist

To finish the quick start, sync results should match selected sources and the verification report should identify items requiring attention. Review a project's context pack: provenance and verification state must be clear. Keep missing data or pricing unavailable. Decide on recurring sync only after these checks.

Sources and next actions

Was this guide helpful?

With analytics consent, your answer helps us choose and improve guides.

Help improve these guides

With your permission, views, clicks, copies, article-end visibility, feedback and broad search topics are stored as daily counts in the project’s Neon database to plan better guides. This analytics payload excludes search text, URL parameters and visitor identifiers. Hosting infrastructure processes network information when receiving requests. Your choice stays in this browser. Revoking consent stops future events, but existing aggregate counts remain.