Verify installation and run the first sync

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

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.

How should you interpret the result?

Keep three checks separate: CLI help confirms command availability; sync uses your real configuration and approved sources; verify inspects the resulting evidence. Do not invent an empty config file: pass the configuration generated by your installation, quoting its path when it contains spaces. On a first run, missing records or context packs may require completing the connection or sync; do not report this as success or zero usage. Resolve path errors against the actual configuration location and source errors in the corresponding tool connection.

A safe example and evidence limits

Command pattern for a path containing spaces: npx personal-agentic-os@latest verify "/absolute/path with spaces/config.json". Replace the placeholder; no successful outcome is claimed for it. On October 3, 2026, verify appeared in public 0.12.0 source help; the Wiki's older execution test used 0.10.0. Neither ran against your personal configuration. For a bug report, provide the version, command name, and a redacted error—not configuration files, private paths, credentials, or conversation text.

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.

Can you retrieve the right project's complete context?

After sync, run npx personal-agentic-os@latest bootstrap /absolute/path/to/config.json <project-id> for an approved project. Its compact output should disclose evidence level and omitted-record counts; brevity does not mean the memory is complete. To inspect an entire category, run details /absolute/path/to/config.json <project-id> "Decision" and follow pagination until next is null. full-context reads that project's complete pack. Review provenance and sensitive data before supplying any output to a model.

Source for this section

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

Related guides

Was this guide helpful?

Your answer is recorded as an aggregate count to help choose and improve guides.