heddle pull

pull brings source history and the native Heddle store — captures, provenance, threads, context, discussions — down from a Heddle remote. That last part is the difference from Git: heddle help git-overlay is explicit that context annotations and discussions move over heddle push / heddle pull to a Heddle remote, and are not projected into Git.

The same 75-versus-76 rule as push applies, with 76 spelled upstream protocol error. 78 means no upstream is configured — print the missing setting rather than retrying.

Arguments

[REMOTE] string optional

Heddle remote name, native repository path, or hosted address.

Flags

--thread <thread>, -t <thread>

Thread to act on.

--local-thread <thread>, -l <thread>

Local thread to update.

--insecure

Allow cleartext (non-TLS) connections to non-loopback hosts. Prefer enabling TLS; use this only for intentional lab/VPN testing.

--lazy hidden

Leave blob content absent by design and hydrate it explicitly later. Hosted/network Heddle remotes only. Real, but absent from --help. See heddle help agent-flags.

Exit codes

Declared by this command's contract, verbatim. Anything not listed contracts only to 0 on success and an unspecified non-zero on failure. The full table and the retry rule — in short, 75 is the only code that is safe to retry.

0

ok

75

remote unreachable; safe to retry

76

upstream protocol error

78

no upstream configured

Examples

Pull from the configured remote

bash$ heddle pull

See also

• heddle push
• heddle clone
• heddle status