English

简体中文

English

简体中文

Check and update a Tool ​

Purpose ​

When the user describes a command, parameter, or output change, read the current version and present a concise four-part plan: changes, version choice, impact, and tool purpose; keep full configuration and internal execution details out of the main display; first run fkit tool info TARGET:VERSION --json to query Flow references. Do not offer update modes until that query succeeds. If locked=true, offer only new-version and state that the old version remains unchanged; if locked=false, ask the user to choose current-version or new-version. Then present the corresponding plan and obtain one confirmation. Check mode is read-only.

Syntax ​

bash
fkit update <TOOL[:VERSION]> [OPTIONS]

Arguments and options ​

  • --mode <MODE> — Select check (default), in-place, or new-version. In conversational updates, first run fkit tool info TARGET:VERSION --json; stop if lock status cannot be queried. Offer both modes only when unlocked; when locked, only new-version is available.
  • --config <FILE> — Tool configuration JSON patch; new-version mode merges it over the selected baseline.
  • --summary <FILE> — Markdown summary replacement.
  • --dry-run — Run local and read-only validation without creation or update requests.
  • --json — Print machine-readable JSON.

Effect ​

Writes, creates, or updates the selected remote object in BioLine.

Safe use ​

Use a Tool name or exact NAME:VERSION; versions must be positive integers. fkit never scans Flow references locally. in-place requires an exact version and at least a config or summary file; BioLine authoritatively rejects edits to a version that a Flow references, and fkit surfaces that error without retrying, changing modes, or creating a fallback version. When config and summary are both supplied, config is written first and summary second in separate, non-atomic requests, and the summary request reuses the command that was just prepared; failures report partial success. new-version reuses the image already stored on the server for the baseline (fkit reads the baseline path automatically and no longer uploads a local image). The create request itself carries the command and summary, so one write normally suffices; fkit then verifies that exactly max+1 was added and reads the new version back to compare its command and summary. If the server did not keep the configuration carried by the create request, fkit issues exactly one repair update against the version it just created and never writes more than that or loops. --dry-run performs local and read-only validation without creation or update requests.

Output ​

Supports --json for check and operation results. New-version output includes before/after versions, baseline, creation verification, configuration verification (configVerified, configSource), and the number of remote writes (remoteWriteCalls).

Read this page ​

Add --docs to read this page from the official BioLine AI documentation service before business arguments are required, sign-in is checked, or the command runs. Choose language with --docs-lang zh|en and use --docs-json for the documentation JSON wrapper. The index and Markdown are fetched from the same official AI service; the index is fixed at https://www.bioline.cloud/ai/commandLineAndFkit/.

bash
fkit update --docs --docs-json --docs-lang en