hosted:node:create
Create a node from --title or the full six-field JSON values file. Without --repository-id the server places it: under --parent, in the parent's repository when you hold a repository write role there, otherwise in your fork. A fork node copies the parents' sharing when all parents are in one upstream repository and you hold a named Editor or Admin grant on every parent; otherwise it starts private unless you have added fork members. With no --parent, create a root in your default workspace. With --repository-id, commit a root in that hosted repository.
Reference for flywheel hosted:node:create.
Create and commit one node. Without --repository-id, the server chooses the repository: with --parent, the node goes into the parent's repository when you hold a write role there and into your fork of that repository otherwise, where it copies sharing when all parents are in the one upstream repository and you hold a named Editor or Admin grant on every parent; otherwise it starts private unless you have added fork members; with no --parent, it becomes a root in your default workspace. The result names the node, the repository it landed in and the placement. With --repository-id, the node is committed as a root in that hosted repository and requires a sufficient repository role. An existing repository refuses insufficient membership with 403 repository_forbidden (CLI exit 3). Instead, to add under a node you can read, run flywheel hosted:node:create --parent <node_id> --title 'My addition'; without a write role there, it lands in your fork. Missing and unreadable parents still return 404, and nothing is created. See Add to a graph you don't own for creation, visibility read-back and sharing.
Initial sharing is copied once at creation; see Sharing when a node is created for the full rule. To review work before publishing it, use a local repository and push only when ready.
Command Group
Hosted Repository
Summary
Create a node from --title or the full six-field JSON values file. Without --repository-id the server places it: under --parent, in the parent's repository when you hold a repository write role there, otherwise in your fork. A fork node copies the parents' sharing when all parents are in one upstream repository and you hold a named Editor or Admin grant on every parent; otherwise it starts private unless you have added fork members. With no --parent, create a root in your default workspace. With --repository-id, commit a root in that hosted repository.
Effect
changes data
Usage
flywheel hosted:node:create [FLAGS]Required flags
None.
Optional flags
| Flag | Value | Default | Choices | Description |
|---|---|---|---|---|
--repository-id | string | Hosted repository UUID to commit to. Omit it to let the server choose the repository. | ||
--parent | string | Parent node UUID, any node you can read; repeat --parent for more parents, and the first one decides the repository. Not with --repository-id. | ||
--title | string | Minimal node title. | ||
--values-file | string | JSON file containing exactly six node fields. | ||
--message | string | Hosted commit message. Only with --repository-id. | ||
--expected-head | string | Hosted head this write expects, as head from flywheel hosted:repository:head <repository_id>. When set, the automatic head read is skipped; if the head has moved, the write is refused with repository_head_mismatch: read the head again and retry. Only with --repository-id. | ||
--format | FORMAT | json, tsv, csv, table | Output format for command results. | |
--env | PROFILE | Select a CLI profile; unconfigured default requires FLYWHEEL_BASE_URL. | ||
--out | PATH | Write output to a file path, or use - for stdout. | ||
--open | Open browser-bound URLs when supported. | |||
--no-retry | Disable transient-error retries. | |||
--retry-max | N | Maximum transient-error retry attempts. | ||
--wait | Block on async operations until a terminal state is reached. | |||
--wait-timeout | SECONDS | 600 | Seconds to wait for --wait before timing out. Defaults to 600. | |
--allow-self | Allow mutating the currently active credential. | |||
--timeout | SECONDS | Set the per-request timeout budget in seconds. | ||
--idempotency-key | KEY | Reuse an Idempotency-Key so ambiguous write failures can be retried with the same key. | ||
--force | Force safety-gated operations where supported. | |||
--yes | Confirm forced compute:release-all --force. Other runtime commands do not read --yes. | |||
--debug | Print structured request debugging with secrets masked. | |||
--verbose | Print verbose progress for long-running operations. | |||
-h, --help | Show this help. |
Examples
Add a node under a node you can read; it lands in the parent's repository or in your fork of it.
flywheel hosted:node:create --parent=<node_id> --title "Next step" --format=jsonCreate a root node in your default workspace.
flywheel hosted:node:create --title "First node" --format=jsonCommit the first graph node with documented null defaults.
flywheel hosted:node:create --repository-id=<uuid> --title "First node"Output
Default format: human.
| Field | Type |
|---|---|
node_id | string |
repository_id (optional) | string |
placement (optional) | "parent_repository" | "fork" | "default_workspace" |
commit_id (optional) | string |
head (optional) | string |
cursor (optional) | string |
receipt_sequence (optional) | integer |
warnings (optional) | array<string> |
hosted:node:branch
Create one branched node and one lineage relation from the source. Only the source's title is copied, not its content, summary, tag assignments or artifacts, and the source is unchanged. Without --repository-id the server places it in the source's repository when you hold a repository write role there, otherwise in your fork. A fork node copies the source's sharing when you hold a named Editor or Admin grant on it; otherwise it starts private unless you have added fork members. With --repository-id, commit it in that hosted repository, which must hold the source.
hosted:node:get
Read one node by node_id: title, slug_name, content, summary, tags, revision (the expected_revision for writes), visibility, can_write and timestamps. owner_email and author_email are included only for nodes you own, hold a repository role on, or that are shared with you by name. Public or link access alone does not include these emails. --projection chooses the fields; full includes at most 40 artifacts, with artifacts_total and artifacts_truncated indicating more. Parent and child IDs are not listed: use hosted:lineage:list.