Skip to main content
Use Node.js 22 or later and an authorized Linktrail checkout with dependencies installed, or your supplied toolkit. These examples use the checkout’s executable path. Replace /path/to/linktrail with its location; run commands from the repository that will own the ledger.
For a check before creating files, use first result. The ledger guide describes file ownership.

​
Connect a hosted project

In the app, select your workspace and open Agent access to create an API credential. Give it the intended project and the sync scopes: projects:read, watches:read, watches:write, events:read, exports:create. Supply the credential through LINKTRAIL_TOKEN in your local environment.
connect reads the workspace and project before saving connection metadata. It keeps the credential out of the saved configuration. LINKTRAIL_API_KEY is also accepted; conflicting credential values are refused. A ledger already connected elsewhere requires a separate ledger for the new identity, so its cursors and mappings stay coherent.

​
Call a shared operation

Generic cloud commands require a matching hosted release. Check availability if the connected server has no command endpoint.
Use call NAME --file arguments.json for a larger JSON object. The catalog lists input schemas and required scopes; local filesystem commands remain separate. Sync and export explains which data crosses the connection. Run doctor when configuration or cloud access fails, then follow troubleshooting.