context
temper context
Manage contexts (projects)
Usage: temper context [OPTIONS] <COMMAND>
Commands:
subscribe Subscribe to a context locally so `temper pull` materializes it. Local config only — this does NOT create the context on the server (use `context create`) and has no server/RBAC effect
unsubscribe Unsubscribe from a context locally (drops it from the local pull set). Local config only — no server effect
create Create a new context on the server
list List the contexts you can see on the server (with owner ref + resource counts)
activity When you last changed something in each context you can read, newest first. Only your own authored changes count: an agent writing under your profile counts, a machine client or a teammate does not, and nothing the system computes does
share Share a context into a team's read-reach. Requires that you administer the context (own it, or manage its owning team) AND manage the target team (owner/maintainer), OR that you are an instance administrator. The context ref is a UUID or the `@handle/slug` / `+team-slug/slug` form (from `context list`); `@me` shorthand is not accepted
unshare Unshare a context from a team (same authority as `share`)
transfer Transfer a context's ownership to a team — the single path to shared authorship (read-sharing stays `share`; writing into a context requires team ownership)
delete Retire a context
restore Restore a retired context, reversing `temper context delete`
rename Rename a context. The slug is derived from the new name — there is no separate `--slug`
shape Orient in a context by its REGIONS: the distilled, region-level view of everything homed there, most salient first. The fastest way to see what a context is about without reading any single resource in it
region-metrics Per-region analytics for a context: centrality, content cohesion, internal tension, reference standing, telos alignment
analytics Context-level staleness: when the shape was last materialized, the latest touch you can see to its regions and edges, and whether the read is stale
changes A context's changes after a position, in commit order
materialize Re-form a context's regions when enough has changed since the last materialize. Below the threshold this is a safe no-op (`materialized: false`). Requires write access to the context
materialize-delta Read a context's formation drift since its last materialize — the read peer of `context materialize`: how many formation events are pending, and whether the threshold clears. Deny is 404 (absent and unreadable collapsed — no existence oracle)
show Show one context by ref
help Print this message or the help of the given subcommand(s)
Options:
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context subscribe
Subscribe to a context locally so `temper pull` materializes it. Local config only — this does NOT create the context on the server (use `context create`) and has no server/RBAC effect
Usage: temper context subscribe [OPTIONS] <NAME>
Arguments:
<NAME> Context name to subscribe to
Options:
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context unsubscribe
Unsubscribe from a context locally (drops it from the local pull set). Local config only — no server effect
Usage: temper context unsubscribe [OPTIONS] <NAME>
Arguments:
<NAME>
Options:
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context create
Create a new context on the server
Usage: temper context create [OPTIONS] <NAME>
Arguments:
<NAME> Context name to create
Options:
--owner <OWNER> Owner of the context: `@me` (default) or `+<team-slug>` for a team-owned context (requires owner/maintainer on the team)
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context list
List the contexts you can see on the server (with owner ref + resource counts)
Usage: temper context list [OPTIONS]
Options:
--retired List retired contexts you ADMINISTER, instead of the contexts you can read. A retired context is invisible to the read path by construction (that is what retirement means), so this is a different axis, not a filter over the same rows — you see a retired context here only if you could have retired it yourself
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context activity
When you last changed something in each context you can read, newest first. Only your own authored changes count: an agent writing under your profile counts, a machine client or a teammate does not, and nothing the system computes does
Usage: temper context activity [OPTIONS]
Options:
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context share
Share a context into a team's read-reach. Requires that you administer the context (own it, or manage its owning team) AND manage the target team (owner/maintainer), OR that you are an instance administrator. The context ref is a UUID or the `@handle/slug` / `+team-slug/slug` form (from `context list`); `@me` shorthand is not accepted
Usage: temper context share [OPTIONS] <CONTEXT> <TEAM>
Arguments:
<CONTEXT> Context ref: a UUID or `@handle/slug` / `+team-slug/slug`
<TEAM> Team to share into: a team slug (optionally `+`-prefixed) or a team UUID
Options:
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context unshare
Unshare a context from a team (same authority as `share`)
Usage: temper context unshare [OPTIONS] <CONTEXT> <TEAM>
Arguments:
<CONTEXT> Context ref: a UUID or `@handle/slug` / `+team-slug/slug`
<TEAM> Team to unshare: a team slug (optionally `+`-prefixed) or a team UUID
Options:
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context transfer
Transfer a context's ownership to a team — the single path to shared authorship (read-sharing stays `share`; writing into a context requires team ownership)
Usage: temper context transfer [OPTIONS] <CONTEXT> <TEAM>
Arguments:
<CONTEXT> Context ref: a UUID or `@me/slug` / `@handle/slug` / `+team-slug/slug`
<TEAM> Target team: a team slug (optionally `+`-prefixed) or a team UUID
Options:
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context delete
Retire a context.
This is REVERSIBLE. The context stops being visible on the read path and stops being writeable, but every row it homes is preserved untouched — nothing is deleted, and the slug is freed for immediate reuse (a fresh context can be created under the old name right away). `temper context restore` undoes it.
The command prints the context id and the mangled ref (`<slug>-retired`, suffixed if that was taken) that `restore` accepts — the original `@owner/slug` no longer resolves once the row is hidden and the slug has moved, so that printed ref is the only address left for it.
Usage: temper context delete [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT>
Context ref: a UUID or `@me/slug` / `@handle/slug` / `+team-slug/slug`
Options:
--vault <VAULT>
Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT>
Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N>
ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR>
Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help
Print help (see a summary with '-h')temper context restore
Restore a retired context, reversing `temper context delete`.
`context` must be a UUID or the **mangled** ref that `delete` printed — NOT the original ref the context had before retirement. The read floor hides a retired context by construction and its slug has moved, so the original address no longer names the row; only the mangled ref (or the bare id) still resolves. `temper context list --retired` also prints it if you did not keep the output from `delete`.
Usage: temper context restore [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT>
Context ref: a UUID, or the mangled ref `delete` printed (NOT the original ref)
Options:
--vault <VAULT>
Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT>
Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N>
ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR>
Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help
Print help (see a summary with '-h')temper context rename
Rename a context. The slug is derived from the new name — there is no separate `--slug`.
THIS RE-ADDRESSES THE CONTEXT. After renaming `@me/temper` to "Temper KB", the ref `@me/temper` no longer resolves and `@me/temper-kb` does. Every stored `@owner/slug` string held by anyone, anywhere, is stale — scripts, agent instructions, bookmarks. Use the `context_ref` in the output as the address from now on (a context UUID never changes, and is the stable thing to store).
Local state is NOT updated: the vault's projected context directory keeps its old name (the next `temper pull` writes a second, new-named directory beside it, and the old one survives with stale files), and a `sync.subscriptions.contexts` entry naming the old slug silently stops matching. Refresh them yourself — re-subscribe with the new ref, and re-run `temper pull` / `temper skill`.
Usage: temper context rename [OPTIONS] --name <NAME> <CONTEXT>
Arguments:
<CONTEXT>
Context ref: a UUID or `@me/slug` / `@handle/slug` / `+team-slug/slug`
Options:
--name <NAME>
The new display name. The new slug is derived from it
--vault <VAULT>
Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT>
Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N>
ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR>
Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help
Print help (see a summary with '-h')temper context shape
Orient in a context by its REGIONS: the distilled, region-level view of everything homed there, most salient first. The fastest way to see what a context is about without reading any single resource in it.
An empty `regions` is not one situation, and `emptiness` names which: `never_clustered` (nothing has been materialized yet — run `context materialize`), `nothing_visible` (materialized, but it formed no regions, or none of them holds anything you can read — the two are one answer on purpose, so this is not by itself a permissions problem), `lens_narrowed` (your `--lens` matched none of the `population` regions you can see here), or `unreadable_or_absent`.
Usage: temper context shape [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT>
Context ref: a UUID or `@me/slug` / `+team-slug/slug`
Options:
--lens <LENS>
Optional lens ref to narrow the read; omit for all lenses
--vault <VAULT>
Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT>
Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N>
ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR>
Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help
Print help (see a summary with '-h')temper context region-metrics
Per-region analytics for a context: centrality, content cohesion, internal tension, reference standing, telos alignment
Usage: temper context region-metrics [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT> Context ref: a UUID or `@me/slug` / `+team-slug/slug`
Options:
--lens <LENS> Optional lens ref to narrow the read; omit for all lenses
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context analytics
Context-level staleness: when the shape was last materialized, the latest touch you can see to its regions and edges, and whether the read is stale.
Three fields, not the five of `temper cogmap analytics` — a context has no charter resource and no regulation set, so there is nothing there to report rather than nothing found. Staleness is reported, never blocking: a stale read is still a read.
Usage: temper context analytics [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT>
Context ref: a UUID or `@me/slug` / `+team-slug/slug`
Options:
--vault <VAULT>
Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT>
Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N>
ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR>
Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help
Print help (see a summary with '-h')temper context changes
A context's changes after a position, in commit order.
Each entry is a pointer — kind, subject (table and id), actor, time and act — never content: read the subject with its own command. A change to a content block names its resource as the subject and the block as `block`. Omit `--after` to start: the answer has no entries and a `through` at the present. Pass an answer's `through` as `--after` to resume, and keep reading while `has_more` is true. A position is opaque and valid only for the context it was issued for.
A change hint, not a cache-invalidation guarantee: the feed never announces an erasure or a scrub, so a mirror must periodically re-read the subjects it holds and drop what is refused.
The consumer contract: record `through` before reading the bodies an answer points at, never after, or a change that commits in between is lost. An edge entry names the edge, not its endpoints, and an edge is in the feed of its own home context only. That home is the source's home when the edge is asserted: a later move of the source leaves the edge where it was. `resource_departed` is a deletion or a move, without saying which. A property scrub is not announced, so re-read what you hold periodically: `open_meta` keys with `resource list --ids … --with open-meta`, facet asserts with `resource facets`, which covers facet asserts only. `resource list --ids` is the cheap periodic sweep.
Usage: temper context changes [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT>
Context ref: a UUID or `@me/slug` / `+team-slug/slug`
Options:
--after <AFTER>
The `through` of an earlier answer for this context. Omit to start
--vault <VAULT>
Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT>
Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--limit <LIMIT>
Page bound, 1..=1000 (default 100). Outside that range is refused, never clamped
--embed-threads <N>
ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--kind <KINDS>
Keep only this change kind (a ledger event-type name). Repeat for several
--color <COLOR>
Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help
Print help (see a summary with '-h')temper context materialize
Re-form a context's regions when enough has changed since the last materialize. Below the threshold this is a safe no-op (`materialized: false`). Requires write access to the context
Usage: temper context materialize [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT> Context ref: a UUID or `@me/slug` / `+team-slug/slug`
Options:
--threshold <THRESHOLD> Formation-event threshold to gate on; omit for the default
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context materialize-delta
Read a context's formation drift since its last materialize — the read peer of `context materialize`: how many formation events are pending, and whether the threshold clears. Deny is 404 (absent and unreadable collapsed — no existence oracle)
Usage: temper context materialize-delta [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT> Context ref: a UUID or `@me/slug` / `+team-slug/slug`
Options:
--threshold <THRESHOLD> Threshold to gate the delta against; omit for the server default
--vault <VAULT> Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT> Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N> ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR> Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help Print helptemper context show
Show one context by ref.
Wraps `GET /api/contexts/{id}` (a decorated ref is resolved first).
Usage: temper context show [OPTIONS] <CONTEXT>
Arguments:
<CONTEXT>
Context ref: `@me/<slug>`, `@<handle>/<slug>`, `+<team-slug>/<slug>`, or a UUID
Options:
--vault <VAULT>
Path to vault (overrides TEMPER_VAULT and auto-detection)
--format <FORMAT>
Output format: json | toon (default: toon on a TTY, json otherwise). Precedence: --format → TEMPER_FORMAT → cli.format config → TTY default
--embed-threads <N>
ONNX intra-op threads for embedding. `0` = let ONNX Runtime decide. Default: this machine's performance-core count (NOT its total core count — efficiency cores measurably slow the batch down). Precedence: --embed-threads → TEMPER_ONNX_INTRA_THREADS → detected → 1
--color <COLOR>
Color output: auto | always | never (default: auto). Precedence: --color → TEMPER_COLOR → cli.color config → NO_COLOR → auto
-h, --help
Print help (see a summary with '-h')Modified at 2026-11-15 01:09:05