Use fx for a manifest-managed workspace. Companion tools own their service APIs and credentials. Outside a managed workspace, use the relevant product tool unless the user explicitly asks for fx.
Run fx self info --format json once when the running version is not yet known.
Keep that executable prefix; its initialization_guide and bundled_skill
identify the instructions shipped with this version.
For a service task, use scoped can/where and keep the returned
execution.binary_path and execution.cwd when calling its companion. A new
shell may resolve the same name to a different installation. Read the companion
Skill for that installation. ready establishes preparation, not every API scope:
verify the operation the user needs before requesting more permissions.
Choose the guide for the user's task:
| Task | Guide |
|---|---|
| Prepare a workspace from a manifest, set up companion tools without one, or resume unfinished preparation | Initialization |
| Query, synchronize or maintain an existing workspace; route a service task; edit the manifest | Workspace tasks |
| Interpret a particular response field or advanced recovery contract | Response contracts |
For initialization, the source and target directory are sufficient. Follow the
initialization guide and preparation.next; it already includes verification.
Continue the user's original task on complete, or hand off the named missing
prerequisites. A list of other fx capabilities is not an initialization checklist.
Read the other guides only when that task or a specific failure needs them.