/ flydocs update
Update project configuration and managed artifacts from the server.
Synopsis
flydocs update [flags] Pulls the latest configuration and framework files from the server, replacing managed artifacts with current versions. This is the command to run when FlyDocs releases new skills, hooks, or commands that you want in your project.
Options
| Flag | Type | Default | Description |
|---|---|---|---|
--path | string | cwd | Project directory to update. |
--here | boolean | false | Use the current directory. |
What It Does
- Wipes managed artifacts (skills, hooks, commands) and replaces them with the latest server templates
- Merges config by pulling server-side changes while preserving local-only fields
- Updates skills to their latest versions based on your workspace configuration
- Cleans up deprecated files that are no longer part of the framework
- Calls sync internally to ensure config and artifacts are fully aligned
Managed artifacts are files owned by FlyDocs (inside .claude/).
Your own code, context files, and knowledge documents are never touched by
update.
If you are actively developing inside a managed path, add it to
artifactOverrides.skipPathsin.flydocs/config.jsonto prevent update from overwriting your changes.
Examples
Update the current project:
flydocs update --here Update a specific project directory:
flydocs update --path ./my-project Related Commands
flydocs sync: Lighter sync without wiping artifactsflydocs init: Full initialization from scratch