openlogos sync
Synchronize all generated files (AGENTS.md, CLAUDE.md, Skills, specs) with the current logos.config.json settings. Run this after manually editing the config or changing the AI tool.
Synopsis
Section titled “Synopsis”openlogos syncNo arguments or options. Must be run from the project root (where logos/logos.config.json exists).
What it does
Section titled “What it does”- Syncs project name in
logos-project.yamlto matchlogos.config.json - Ensures
documents.changessection exists inlogos.config.json(adds it if missing) - Regenerates
AGENTS.mdbased on current locale, AI tool, and lifecycle - Regenerates
CLAUDE.mdbased on current locale, AI tool, and lifecycle - Re-deploys Skills to the appropriate target directory
- Re-deploys specs to
logos/spec/ - OpenCode only: Re-deploys plugin, syncs
opencode.jsonpermissions, re-deploys slash commands
Example output
Section titled “Example output”Syncing project files...
✓ logos-project.yaml name synced to "my-project" ✓ documents.changes added to logos.config.json ✓ AGENTS.md updated ✓ CLAUDE.md updated ✓ 13 skills synced to logos/skills/ ✓ 8 specs synced to logos/spec/
Sync complete.When to use
Section titled “When to use”- After editing
logos/logos.config.json(changing name, locale, or AI tool) - After upgrading the
openlogosCLI to a new version (to get updated Skill content) - When switching AI tools mid-project (e.g., from Cursor to Claude Code)
- After running
openlogos launchif you need to force-regenerate files
Errors
Section titled “Errors”| Error | Cause | Fix |
|---|---|---|
logos/logos.config.json not found | Not in project root, or project not initialized | cd to project root, or run openlogos init first |